Zapier & Make Connectors
Connect Flash to thousands of apps without writing code. In Zapier or Make, a Flash event can start a workflow anywhere — and those workflows can push data back into Flash. There's no separate integration to install: connectors are built on the same webhooks and v2 REST API documented here.
Three parts, all already built
Every no-code automation is made of a trigger, one or more actions, and an authentication method. Flash provides all three from its existing platform surface.
Triggers = webhook events
A connector's trigger list is exactly the live event catalog — member created, tier upgraded, order placed, and so on.
Actions = v2 endpoints
An action calls a v2 REST endpoint — create a member, award points, issue a coupon, add a custom-object record.
Auth = a scoped API key
The connector authenticates with a fl_live_ key sent as Authorization: Bearer, scoped to just the actions and events it needs.
The REST Hook contract
Zapier's REST Hook model (and Make's instant triggers) maps straight onto the Flash webhook endpoints — no extra backend. A REST Hook subscribes to exactly one event; when the user turns a Zap off, it unsubscribes. All three lifecycle steps use a webhooks:manage key.
| REST Hook step | Flash call | Notes |
|---|---|---|
| subscribe | POST /api/v2/webhooks | { url, eventTypes: [event] } → the response data.id is the subscription id. |
| unsubscribe | DELETE /api/v2/webhooks/{id} | The id stored at subscribe time. |
| perform | (the delivered POST body) | The thin payload Flash delivers when the event fires. |
# subscribe (what the connector does when a Zap turns on)
curl -X POST https://flash.socialhub.ai/api/v2/webhooks \
-H "Authorization: Bearer fl_live_..." \
-H "Content-Type: application/json" \
-d '{ "url": "https://hooks.zapier.com/...", "eventTypes": ["member.created"] }'
# 201 { "data": { "id": "whe_..." } } <-- stored as the subscription id
# unsubscribe (Zap turned off)
curl -X DELETE https://flash.socialhub.ai/api/v2/webhooks/whe_... \
-H "Authorization: Bearer fl_live_..."Push data back into Flash
An action is just a call to a v2 endpoint with the key's scopes. Give the connector's key only what it needs — for example members:write to create members, or objects:write to add custom-object records — and every call is authenticated and audited like any other API request.
# example action: upsert a member when something happens in another app
curl -X POST https://flash.socialhub.ai/api/v2/members \
-H "Authorization: Bearer fl_live_..." \
-H "Content-Type: application/json" \
-d '{ "email": "ada@example.com", "fullName": "Ada Lovelace" }'Create and scope keys in Account → API Keys. Browse every available action in the REST API reference.