With the ReceptionWorks app in Zapier, a Zap can start the moment something happens in your business: a new booking, a new conversation, a request for a team member or a support request. You do not copy any addresses: Zapier subscribes by itself, and the receiver appears in the “Webhooks” tab.
Where to find it
Open “Modules” in the top menu, connect the “Integrations” module (it is off by default) and click “Open integrations” on its card. The “Connections” tab opens. Only the Owner and the Administrator can connect Zapier.
Connect in one step
- On the Zapier card click “Connect Zapier”. A key named “Zapier” is created and appears once.
- Click “Copy key and open Zapier”: the key is copied and Zapier opens in a new tab.
- If the key could not be copied, select it and copy it by hand. If you lose it, revoke the key and connect again.
Keep the key private: whoever has it can subscribe to the events of your business, including customer contacts. A business can have up to 10 active keys, so make a separate key for each Zapier account.
On the “API keys” tab you can also create a key with your own name, for example for a second Zapier account: type the name, click “Create key”, then “Copy key”.
Connect in Zapier
- In the Zapier tab accept the invitation to the ReceptionWorks app if Zapier asks, then create a Zap and choose ReceptionWorks as the trigger.
- Choose the event. Zapier shows event names in English, for example “New Booking”.
- When Zapier asks you to connect an account, paste the key.
- Test the trigger. Zapier shows recent events of your business. If there are none yet, create one, for example by starting a conversation in your chat, and test again, or skip the test: Zapier then uses an example.
- Turn the Zap on.
“New message” and “Conversation transcript” carry the full text of conversations, so use these triggers only in Zaps you trust.
What you see in ReceptionWorks
- In “Webhooks” the receiver of a Zap is marked “Created from Zapier” with the key name. Zapier manages its address, so here you can only pause or delete the receiver. When you turn a Zap off or delete it, Zapier removes the receiver itself.
- Such receivers do not count toward the limit of 5 manual receivers; there can be up to 50 of them. Delivery, retries and the delivery log work as for any receiver.
- In “API keys” each key shows when it was last used and how many Zap triggers are connected.
Revoke a key
Click “Revoke” on the key, then “Revoke key”. Zaps connected with this key stop receiving events immediately and their receivers are deleted. This cannot be undone: create a new key and reconnect the app in Zapier. A key is also revoked automatically when the person who created it is removed from the team or the business is archived; the list then shows the reason.