Integrations

The Integrations page is a grid of cards, one per partner. Each card has a short description and a Connect button.

• Slack (Notifications) — forward replies that no automated follow-up handled to a Slack channel. Available now.
• HubSpot (CRM) — sync contacts, lifecycle stages, and campaign engagement back to HubSpot.
• Adora (POS) — connect ordering and customer activity from Adora to power targeted messaging.
• Message Forwarding (Webhook) — send every incoming message to a URL you own. Available now.
• API Access (API) — issue keys so your own systems can call the RCSync API. Available now.

Connect a Slack channel and RCSync will post there whenever a contact replies and no automated follow-up matches — the same replies that show up on your Inbox. This is the fastest way to notice a customer who needs a human.

• Connect — In Slack, create an Incoming Webhook for the channel you want, then paste its URL into the Slack card on the Integrations page. We send a one-time test message to confirm it works.
• Choose senders — On the Inbox page, open Slack notifications and switch on the senders you want forwarded. New senders are off by default, so nothing is forwarded until you opt in.
• Every unhandled reply is covered — Any free-text reply that no follow-up handles shows up on the Inbox automatically, including replies to plain broadcasts without interactive follow-ups. The per-sender switches above control which of those also post to Slack.

Point RCSync at a URL you control and every incoming message to your brand is POSTed there as it arrives — one JSON request per message. Use it to land replies in a help desk, a CRM, or your own automation, without waiting for a purpose-built integration.

Unlike Slack notifications, which only cover replies no automated follow-up handled, forwarding covers every inbound message on the senders you own: free-text replies, button taps, shared files and locations, and STOP/START/HELP keywords. Forwarding is a copy — it never changes how a message is handled in RCSync, and consent keywords still take effect exactly as before.

Open the Message Forwarding card and set:

• Destination URL — must be https and publicly reachable. Local and private addresses are rejected when you save.
• Authentication — whichever method your endpoint expects: a bearer token, basic authentication, a custom header, an HMAC-signed request, or none. The credential is encrypted at rest and never shown again once saved.
• Channels — switch RCS and SMS on or off independently, so you can forward one channel and not the other.
• Send test message — posts a synthetic message to your endpoint and reports the response, so a wrong URL or credential fails here rather than on a real reply.

Someone has to build the endpoint that receives these. Send them the API reference — it covers the exact headers we send, how to verify an HMAC signature, the payload field by field, and the delivery contract (one attempt, no retry, dedupe on the message id).

Open the API Access card to create and revoke API keys. Create one per system you want to give access to, so revoking a partner never disturbs the others. A key is shown once at creation and stored only as a hash — a lost key is replaced rather than recovered, and revoking one takes effect immediately.

Today a key authenticates the consent lookup endpoint, which answers whether contacts have opted out. See Consent → Checking opt-out status from your own system for the request, the response, and its limits.

Even before integrations land, you can move data in and out:

• CSV uploads for campaign audiences. See Audiences.
• Open campaigns let external systems trigger sends by hitting a webhook URL with a JSON payload. See Campaign types → Open.
• CSV exports from the Analytics page for downstream reporting.
• Consent exports from the Consent page, when you want the whole suppression list rather than an API lookup.