Skip to the operations

CRM

RD Station CRM in a decision flow.

7 RD Station CRM operations a decision flow can call directly, with the credentials your own contract issued. The response is data the rest of the flow reads, branches on, and keeps in the trace.

Category
CRM
Type
Integration
Authentication
API key
Test environment
Production host only

Who they are

The sales CRM in RD Station's Brazilian marketing and sales suite.

RD Station CRM tracks deals through a funnel and sits alongside RD Station Marketing, the automation product the company is better known for. It is widely used by Brazilian small and mid-sized businesses, which makes it the CRM a Brazilian sales team is most likely to already have. The two products have separate APIs and separate credentials.

What a flow can call

7 operations, each one a step you can place on the canvas.

  1. PUT/deals/$data.rd_deal_id

    Write the outcome to a deal

    Moves the negociação to the stage the decision implies and records why.

  2. GET/deals/$data.rd_deal_id

    Read a deal

    The deal's current state with its custom fields.

  3. PUT/deals/$data.rd_deal_id

    Mark a deal as lost

    Closes the deal as lost with a reason, which is the honest way to record a decline.

  4. GET/contacts?email=$data.applicant_email

    Find a contact

    Looks a contact up by email before anything writes to it.

  5. PUT/contacts/$data.rd_contact_id

    Update a contact

    Writes back to the person rather than the deal — the right place for something durable the decision established, such as a phone number a verification step confirmed, as against the outcome of one application.

  6. GET/deal_stages

    List deal stages

    Every stage in every funnel, with its id. Run this once when setting the connection up and pin the ids the flow needs — they differ per account, so a flow that hard-codes them from another environment moves nothing.

  7. GET/users

    Verify the token

    Lists the account's users. Cheapest way to confirm the token works and that it belongs to the instance you expected.

Where it sits in the decision

CRM calls have a natural place in a flow.

Writing the outcome back closes the loop with the commercial team, so the record they work from carries the same verdict the customer received rather than a copy that drifts.

Whatever RD Station CRM returns is part of the run, so it is part of the record. When someone asks months later why an applicant was declined, the answer cites what came back at the time rather than re-fetching from a service whose answer has since changed.

  • 01Add RD Station CRM as a connection authenticating with an API key.
  • 02RD Station CRM has one host for both environments, so guard test runs with your own credentials and limits.
  • 03Place a Connection node and pick an operation — “Write the outcome to a deal” is usually the first one a flow needs.
  • 04Map the response into the fields your rules read, then test the whole path before it carries live traffic.

Common questions

Using RD Station CRM in a flow.

How do I connect RD Station CRM to a decision flow?

Add RD Station CRM as a connection in your workspace authenticating with an API key, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use RD Station CRM in a decision without ever seeing the secret.

Can I test RD Station CRM without touching production?

RD Station CRM exposes one host for both environments, so there is no separate sandbox to point at. Test runs still execute in Sandbox and are recorded separately in decision history, but the call goes to the same place as production — so guard it with your own test credentials, rate limits, or data.

What can a flow call on RD Station CRM?

7 operations, including “Write the outcome to a deal”, “Read a deal”, “Mark a deal as lost”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Write the outcome to a deal”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.

Where in a decision should RD Station CRM be called?

Writing the outcome back closes the loop with the commercial team, so the record they work from carries the same verdict the customer received rather than a copy that drifts.

Also in CRM

Ready when you are

Wire RD Station CRM into a real decision.

Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.

Read the docs