Integrations

If it speaks HTTP, it connects.

Flash Chat sends signed webhooks out and takes forty-eight API endpoints in. That is enough to reach your shop, your CRM, your payment provider and your spreadsheets, without waiting for us to build a connector for each one.

Straight answer first: these are not one-click apps.

You wire them up with our webhooks and API, either directly or through Zapier, Make or n8n using their HTTP steps. There is no published Flash Chat app in those marketplaces yet. Everything named below works today by that route, and we would rather say so than let a wall of logos imply otherwise.

What people connect

The things businesses actually wire up.

Each of these is a real pattern, with the route it takes written underneath.

Automation platforms

The quickest path if you would rather not write a server. Catch our webhook, call our API, done.

ZapierMaken8nPipedream

Webhooks by Zapier · Make HTTP · n8n HTTP Request

Online shops

Order confirmations, dispatch notices and delivery updates, sent the moment the shop fires its own webhook.

ShopifyWooCommerceMagentoSalla

Shop webhook → your endpoint → POST /v1/messages

CRM and sales tools

Push a new lead into a follow-up sequence, and write replies back onto the record.

HubSpotZohoPipedriveSalesforce

/v1/contacts · /v1/sequences/{id}/enroll · message.received

Payments

Send the receipt when the payment clears, and chase the ones that do not.

StripeRazorpayPaytmTap

Payment webhook → POST /v1/messages

Spreadsheets and internal tools

Keep a sheet of contacts in step, or trigger a message from a row somebody ticks.

Google SheetsAirtableNotionRetool

Apps Script, or a scheduled Zap calling /v1/contacts

Ads and lead sources

A lead form fills in, and the first WhatsApp message is waiting before they close the tab.

Facebook lead adsInstagramGoogle AdsWeb forms

Lead webhook → /v1/contacts → enrol in a sequence

The two halves

What comes out, and what goes in.

Every outbound payload carries a timestamped signature, so your server can prove the event came from us before acting on it.

Events we send you Signed, and delivered to any URL you name

message.received A customer wrote to you, on WhatsApp or SMS
message.status_updated Something you sent was delivered or read
conversation.created A thread was opened with somebody new

What you can call Forty-eight endpoints across nineteen resources

/v1/messages Text, media, templates and buttons
/v1/contacts Create, tag and deduplicate
/v1/sequences Build follow-ups and enrol people
/v1/broadcasts Launch, pause, resume, cancel
/v1/otp Send and check a login code
/v1/validate Is this number on WhatsApp?

A worked example

An order confirmation, end to end.

1 A customer checks out, and your shop fires its order webhook.
2 Your handler, or a Zap, receives it and reads the phone number.
3 It calls Flash Chat with the message and the number to send from.
4 The reply lands in your shared inbox, so support sees the whole thread.

Opted-out customers are refused at this step, whichever route the call came from, so a shop integration cannot message somebody who has asked you to stop.

Your handler, on the shop's order webhook

# Same call whether the channel is WhatsApp or SMS.
curl -X POST https://app.flashchat.xyz/api/v1/messages \
  -H "Authorization: Bearer $FLASHCHAT_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+966500000000",
    "channel_id": "a1c9…",
    "type": "text",
    "text": "Order #1042 confirmed — out for delivery tomorrow."
  }'

Built in

Three things that need no integration at all.

These are part of the product rather than something you wire up.

WhatsApp Cloud API

Meta's official channel, connected from Settings. Templates, media and the service window handled for you.

A phone you already own

Scan a QR code and the number is linked, the way WhatsApp Web is. Your phone keeps working.

Android SMS gateway

Our app on a handset with your SIM turns it into a sender, for people who are not on WhatsApp.

Get started

Create a key and make the first call.

Keys are scoped, so an integration only gets what it needs. The free plan includes one, which is enough to wire something up and see it work.

Start free → See the API