RD Station API
brisk4 consumes the public API of RD Station Marketing and RD Station CRM, authenticated with OAuth 2.0.
Integration · Marketing and CRM
Official WhatsApp + RD Station.
brisk4 closes the loop between demand generation in RD Station and customer service on WhatsApp. A lead converting on a form is approached within minutes, and what happens in the conversation flows back to RD as a conversion event and a deal update.
What syncs
RD Station objects inside the conversation.
| RD Station object | Direction | Trigger |
|---|---|---|
| Lead (Contact) | RD → brisk4 | A form or landing page conversion triggers WhatsApp outreach within minutes. |
| Conversion event | brisk4 → RD | Meaningful chat interactions become conversion events, feeding lead scoring and automation. |
| Deal (RD CRM) | brisk4 ↔ RD | An AI-qualified lead creates the deal; a stage change in the CRM fires a message. |
| Tags and segmentation | brisk4 → RD | Interest identified in the conversation applies the matching tag for email nurture flows. |
| Opt-out | brisk4 ↔ RD | An unsubscribe requested on WhatsApp propagates to RD, and vice versa, keeping the base compliant. |
Ready-made flows
What goes live first.
- Speed to lead in minutesA conversion on the RD form fires the webhook, and brisk4 reaches out over official WhatsApp while the lead is still warm, with an approved template, before a competitor answers.
- Lead scoring fed by the conversationWhat the lead says in chat becomes a conversion event in RD: product interest, budget, timing. Scoring stops depending on email clicks alone.
- Nurture that respects the channelIf the lead is already chatting on WhatsApp, brisk4 tags them in RD and the email flow pauses. No customer receives the same offer through two channels.
How we connect
Method and prerequisites.
Conversion webhook
RD notifies brisk4 at the moment of conversion, which is what makes minute-level outreach possible without periodic polling.
Custom events
Chat interactions are sent as custom conversion events, available for automation and segmentation inside RD.
- Covered products
- RD Station Marketing and RD Station CRM
- Required access
- Authorised app in your RD account
- Authentication
- OAuth 2.0
- Opt-in
- A base with valid consent for WhatsApp contact
- Templates
- First-contact messages approved on the Meta Official API
- RD plan
- API and webhook features according to your RD Station plan
Frequently asked questions
RD Station and brisk4: questions.
How fast is an RD lead approached on WhatsApp?
Within minutes. The form conversion fires a webhook to brisk4, which sends the first-contact message through a template approved on the Official API. There is no periodic polling and no batch job to wait for.
Does the conversation flow back to RD Station?
It does. Meaningful interactions become conversion events in RD, feeding lead scoring, segmentation and automation. Interest tags identified by the AI are written to the contact too.
Can I use brisk4 with RD Station Marketing only, without the CRM?
Yes. The Marketing integration covers conversions, events and tags. If you do not use RD Station CRM, the pipeline can live in brisk4 own CRM module.
How is opt-out handled between email and WhatsApp?
Unsubscribes propagate both ways. Anyone asking to stop receiving WhatsApp messages has that reflected in RD, which keeps the base compliant with the LGPD and with Meta policies.
Close the loop on your RD.
In the free assessment we map your conversions, lead volume and where response time is costing revenue.