Data sources

RB2B integration

In short

How does Reply's RB2B integration work?

RB2B posts identified visitors into Reply one at a time, using a URL that carries its own token. Each contact can be added to lists and pushed into a sequence. It is one-way (Reply never sends anything back) and a call can be rejected for reasons worth knowing in advance.

At a glance


Availability	Available. Included on plans that offer the RB2B integration – check yours in Billing
Direction	One-way: RB2B → Reply
Sync timing	Immediate. Each identified visitor is posted as it happens
What you need	An RB2B account that can send to a webhook URL
Surfaces	Setup: the URL is generated in the app and pasted into RB2B. Once live: arriving contacts are readable through the API and MCP, and raise webhook events like any other contact
Does not	Send anything back to RB2B · accept more than one contact per call · bypass your contact allowance

Availability

Available on plans that include the RB2B integration. On the RB2B side you need to be able to configure an outbound webhook: check that before setting anything up in Reply.

How to connect RB2B

Before you start

Confirm your RB2B plan can send to a webhook
Decide where arriving contacts should go: a list, a sequence, or both

Connect

In Reply, open Integrations and choose RB2B. Reply generates a URL containing a token unique to your account.
Copy it and paste it into RB2B as the destination for identified visitors.
Optionally choose the lists and the sequence arriving contacts should join.
Trigger a test from RB2B and confirm a contact appears in Reply.

The URL is the credential. Anyone holding it can post contacts into your account, so treat it as you would an API key; do not paste it into a shared document or a ticket.

What to expect

What arrives

Data	Direction	When	Notes
Identified visitor	RB2B → Reply	Immediately	One contact per call
List membership	–	On arrival	If configured
Sequence enrolment	–	On arrival	If configured

After you connect

Contacts arrive continuously rather than in batches, and each is handled on its own. A contact that already exists is matched rather than duplicated.

When a call is rejected

Reply refuses a contact rather than half-creating one. The reasons worth knowing:

The token is not recognized – usually a copy-paste error, or the integration was removed in Reply
The sequence or a list no longer exists – the call names one Reply cannot find
Your contact allowance is used up – no new contacts are created until it resets. See Why did I hit the active contacts limit?
The contact data is not usable – a missing or invalid address

What doesn't happen

Nothing goes back to RB2B. Replies, sequence outcomes and status changes stay in Reply.
No bulk import. One contact per call, by design.
No bypassing limits. Arriving contacts consume your contact allowance like any other.

Common problems

Contacts stopped arriving – check your contact allowance first, then that the sequence and lists named in the setup still exist.
Nothing ever arrives – confirm RB2B is actually sending, and that the URL was copied complete, including its token.
Contacts arrive but do not enter the sequence – check the sequence is active and that they are not being skipped. Full guide

Pause or disconnect

Stop sending from RB2B to pause without changing anything in Reply. Removing the integration in Reply invalidates the token, so any further calls are rejected; if you reconnect later you will get a new URL and must update RB2B.

FAQ

Does Reply send anything back to RB2B?

No. The connection is one-way.

Can RB2B send a batch of contacts?

No. One contact per call, as they are identified.

Do RB2B contacts count towards my allowance?

Yes, exactly like any other contact.

Is the URL secret?

Yes. It is the only credential, so treat it as you would an API key.

Need help connecting RB2B?

If the connection fails or data isn't syncing the way you expect, the Reply support team can check your integration settings with you. Open the Reply Help Center and send the team a message.