Integration guide
Connect Response360 to your other tools
This guide gathers every way to connect Response360 to the tools and channels your business already uses — from setting up your customer channels (WhatsApp, website chat, email) to streaming order notifications and CRM automations into your account with an account-specific API key and signed webhooks. Jump to whichever section you need below.
The status labels are honest: Live = you can use it today. Via Zapier = it connects through an automation tool like Zapier/Make rather than a one-click app. On the roadmap = we're working on it.
Customer channel
WhatsApp is Response360's most mature channel. Your customers message you on WhatsApp; messages land in your unified inbox, the AI auto-answers the suitable ones from your own content, and routes sensitive or unclear ones to an agent.
Connecting your WhatsApp number
A WhatsApp number is connected through Response360 from Channels → WhatsApp in the panel. Because business messaging on WhatsApp requires an official approval process, Response360 handles activating your number on your behalf — we take care of the required provider/Meta approvals. So on first setup, after you share your business details, we open the channel for you; from then on the inbox, AI and campaigns are under your control.
Once the channel is connected, WhatsApp shows as Connected on the Channels screen and you start receiving messages.
Incoming messages and AI triage
When a customer message arrives, Response360 follows this order — the AI never invents information, it only answers from the content you defined:
- 1Sensitive-topic check. If the message falls under one of the sensitive topics you defined, the AI produces no answer at all — it is routed straight to an agent.
- 2Ready answer (FAQ). If the question matches one of the FAQ answers you wrote in advance, the AI picks that answer and sends it.
- 3Knowledge base. If no FAQ matches, the AI may compose a reply by quoting only the documents you added to the
Knowledge Base; if it isn't confident enough it still hands off to a human. - 4Otherwise, to a human. On any uncertainty the conversation drops into the human queue; an agent answers from the inbox.
You edit your FAQ and knowledge-base content in the panel under Knowledge Base and the FAQ sections, and sensitive topics under Settings. How much work the AI takes over depends entirely on this content.
Campaign and template sending
From the Campaigns section in the panel you can send a bulk WhatsApp message to a customer list. Per WhatsApp's rules, sends outside the 24-hour reply window require a pre-approved template. You define your templates in the panel and submit them for approval, then select the approved ones in campaigns. The campaign screen also provides a delivery funnel, per-recipient results, test sends and cancellation.
Where to get it
There is nothing to download or install for WhatsApp. Connect it in the panel under Channels → WhatsApp and Response360 activates the number for you.
Customer channel
Website chat
Add a live chat bubble to your website. Visitors write from the site, messages land in the same inbox and pass through the same AI triage as WhatsApp (sensitive → human, FAQ/knowledge base → auto-answer).
Embed snippet
Add the snippet below just before the </body> tag on every page where you want the chat to appear. Get the TENANT_KEY value in the panel under Channels → Website chat. This key is not an API secret — it can safely appear in your page HTML.
Website chat embed snippet
<script src="https://app.response360.io/webchat.js" data-key="TENANT_KEY" async></script>On WordPress you can also paste it into your theme footer or a “header/footer scripts” plugin. No other file or setup step is needed.
Appearance, pre-chat form and satisfaction survey
In the panel under Channels → Website chat you customize the widget with a live preview: color/theme, position, launcher text, logo and avatar, greeting messages; a pre-chat lead form (name, email, phone — each toggleable optional/required, with an optional GDPR consent notice and checkbox) and a post-chat satisfaction survey (CSAT).
Allowed domains (security)
To make sure the widget only runs on your own site, use the Allowed domains setting. If you enter a list of domains, the widget only runs on those sites; it won't open even if embedded elsewhere. If you leave it empty the widget runs anywhere. We recommend adding your own domains.
Where to get it
The embed snippet lives in the client panel under Channels → Website chat — copy it from there. No plugin or download required.
Customer channel
Send campaign and notification emails from your own domain. To prove the emails really come from you (and to stay out of spam), Response360 verifies your sending domain with DKIM / SPF / DMARC.
Verifying your sending domain
- 1In the email-domain section of the panel, use
Add domainto enter your domain and sender address. - 2Response360 gives you the DNS records to publish: three
DKIMCNAME records, a recommendedSPFTXT record and an optionalDMARCTXT record. Each record's name and value comes with a copy button. - 3Add these records at your domain's DNS provider, then press
Verify / refreshin the panel. Once the records are detected the status becomes Verified and sending from that domain is enabled.
Multiple domains and sender selection
You can verify multiple domains. Mark one as the default sender with Make default (★). When creating a campaign you can choose which verified domain to send from; if you don't, the default domain is used.
Email composer
You build your email campaigns with a drag-and-arrange block-based composer: heading, text, image, button, list, divider, spacer, and — for advanced use — raw HTML blocks; alignment and style controls; saved templates; merge fields like {{ad}} and {{sirket}} and an automatic unsubscribe / GDPR footer. You see desktop and mobile previews live as you edit.
Where to get it
Email sending is built into the client panel — no download. Add and verify your domain in the panel, then compose in Campaigns.
Foundations
API key + webhooks
Every automation on Response360 is built on two things:
(a) API key
An account-specific secret key created in the panel under Integrations. It authenticates every request going to Response360 (such as sending a message). Keep the key secret; use it server-side only.
(b) Signed webhooks
Notifications going out from Response360. When a message arrives, the AI answers, or a conversation is handed to a human, it sends an event to the address you set.
Where to get it
Create your API key and manage webhooks in the client panel under Integrations (also available at /integrations). You'll find sample payloads and a signature-verification guide there too.
API base URL and auth
All API calls go to https://api.response360.io. Authentication uses the Authorization: Bearer <API_KEY> header (alternatively an X-API-Key: <API_KEY> header is accepted). The recommended way to send anything is to fire a flow (below) — one endpoint that runs your no-code automation.
Recommended: fire a flow — POST /v1/flows/{id}/trigger
Build a no-code flow in the panel (a trigger → conditions → actions graph), then fire it from an external event with a single call. Pass to (recipient) and a variables object; the flow sends an approved WhatsApp template and/or an email from your own domain, fail-safe (it enforces opt-in and the approved-template rule, and triages any reply). The flow must be enabled with an api trigger.
Fire a flow — cURL
curl -X POST https://api.response360.io/v1/flows/FLOW_ID/trigger \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"to": "905551234567",
"variables": { "name": "Alex", "order_no": "1043" }
}'
# The flow sends the approved WhatsApp template and/or an
# email from your own domain — fail-safe.Advanced: direct sends (opt-in)
The low-level direct-send endpoints — POST /v1/messages (WhatsApp text/template) and POST /v1/email (own-domain email) — are opt-in / scope-gated for transactional or advanced use. Most integrations should prefer the flow trigger; ask us to enable the send scopes on your key if you need them.
Configuring webhooks and verifying signatures
In the panel under Integrations → Webhooks add a webhook address and select the events you want to listen for. Available events:
message.receiveda new customer message arrivedanswered_by_aithe AI auto-answered from your contentescalated_to_humanthe conversation was handed to a humanhuman.repliedan agent repliedbroadcast.completeda bulk send finisheddelivery.statusdelivery status (delivered/read)
Every webhook request is signed. Response360 computes an HMAC-SHA256 over the raw request body with your endpoint secret and sends it in the X-Response360-Signature header as sha256=<hex>. We strongly recommend verifying this signature before processing each incoming request — so you know it truly came from Response360.
Signature verification — Node.js example
const crypto = require("crypto");
function verify(rawBody, headerValue, endpointSecret) {
const expected =
"sha256=" +
crypto
.createHmac("sha256", endpointSecret)
.update(rawBody) // raw body (unparsed)
.digest("hex");
return crypto.timingSafeEqual(
Buffer.from(headerValue),
Buffer.from(expected)
);
}
// headerValue = req.headers["x-response360-signature"]Automation
Zapier
Honest note: a published one-click Response360 Zapier app is on our roadmap — but you can connect a Response360 Zapier app today via API-key auth, or wire it up in both directions with Zapier's generic Webhooks by Zapier building block.
Where to get it
In Zapier, search for the Response360 app (or use the CLI app the partner provides) and connect it with an API key generated in the client panel under Integrations → API keys. No key? Create one first, then paste it into Zapier's connection step.
Response360 → Zapier (triggers)
Start a Zapier flow from an event in Response360 (e.g. create a Google Sheet row when a new message arrives).
- 1In Zapier create a new Zap; choose
Webhooks by Zapier → Catch Hookas the trigger. - 2Copy the Custom Webhook URL Zapier gives you.
- 3In the Response360 panel under
Integrations → Webhooksadd this URL as a new webhook address and select the events you want (e.g.message.received). - 4For security, add a verification step on the Zapier side to validate the
X-Response360-Signatureheader with the HMAC-SHA256 method above.
Zapier → Response360 (actions)
Send a WhatsApp message through Response360 from an event in another app (e.g. send a welcome message when a new record is added to your CRM). For richer, multi-channel automations point the same POST at the flow trigger (/v1/flows/{id}/trigger) instead — the direct /v1/messages send is opt-in.
- 1In the Zap's action step choose
Webhooks by Zapier → POST. - 2In the URL field enter
https://api.response360.io/v1/messages. - 3Under Headers add
Authorization=Bearer YOUR_API_KEY. - 4Set the payload type to
jsonand map the fields from the previous step into the body:to= customer number,text= message text.
Zapier POST body (json)
{
"to": "{{crm_phone}}",
"text": "Hi {{crm_first_name}}, welcome aboard!"
}E-commerce
Shopify
Honest note: we don't yet have a native Shopify app — that's on our roadmap. Today Shopify connects to Response360 as a self-hosted webhook relay (source in the repo under integrations/shopify, set up by the partner) or through an automation tool. Two paths:
Where to get it
The Shopify relay is a small self-hosted Node service (repo integrations/shopify) that verifies Shopify's HMAC and calls /v1/messages. The partner deploys the relay and registers the Shopify webhooks for you. Prefer no-code? Use Zapier/Make instead (Path A below).
Path A — via Zapier / Make
Connect Shopify triggers (new order, abandoned cart, fulfillment) to Response360's /v1/messages endpoint with an automation tool. Follow the same Zapier → Response360 steps above; just pick Shopify as the trigger app.
Path B — the self-hosted relay / custom integration
Point Shopify Webhooks or Shopify Flow at the self-hosted relay (integrations/shopify) or your own endpoint, which then calls the Response360 API. This suits scenarios where you need full control of the body (personalization, conditions).
Example — order confirmation / abandoned-cart message
POST https://api.response360.io/v1/messages
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
{
"to": "905551234567",
"text": "You left items in your cart. Want to finish checkout? 🛒"
}CMS & e-commerce
WordPress / WooCommerce
This is a real, installable plugin. It adds a click-to-WhatsApp widget to your WordPress site and sends an automatic WhatsApp notification on WooCommerce orders.
Download the plugin
Download the ready-to-install plugin zip below. It's the same package we ship — no build step, just upload it to WordPress.
response360-wordpress.zip · install via WP Admin → Plugins → Add New → Upload Plugin
Installation
- 1In WP Admin, go to
Plugins → Add New → Upload Plugin, choose theresponse360-wordpress.zipfile you downloaded, and clickInstall Now. (Alternatively, unzip and upload theresponse360folder into/wp-content/plugins/.) - 2Click Activate once the upload finishes (or activate it from the
Pluginsscreen). - 3Open the
Settings → Response360page. - 4In the API Key field, paste the key you created in the panel under
Integrations → API keys. Leave the API Base URL field at its default. - 5Configure the widget and/or WooCommerce notifications.
- 6Save changes — you're live.
Click-to-WhatsApp widget
In the Click-to-WhatsApp widget section of settings, turn it on with Enable widget and fill in: WhatsApp number, Prefilled message, Button label, Position, Button color and an optional Custom link. The widget is added to the page as a wa.me link — it never exposes your API key to the client side.
WooCommerce order notifications
In the WooCommerce order notifications section, turn it on with Enable notifications and pick which order statuses trigger a message with Notify on statuses. Edit the message text in the Message — order received and Message — order completed fields. When an order moves to a selected status, the plugin makes the POST /v1/messages call server-side on your behalf.
Placeholders you can use in messages:
{order_number}{first_name}{total}{site}
Note: sending a notification never blocks the checkout flow; if an error occurs it is recorded as an order note.
Need help? In the panel's Integrations section you can manage your API key and webhooks and view sample payloads and the signature-verification guide. For questions, write to [email protected].