⬜ Zapier

Zapier is an online service that automatically connects thousands of apps together (Gmail, Slack, Google Sheets, Discord, Airtable, etc.), with no coding needed. The Zapier block lets your Celestory story send a piece of information to Zapier, which then passes it on to the app of your choice.

This block is useful whenever you want your project to trigger an action outside of Celestory: sending a message, saving data to a spreadsheet, notifying someone, and so on.

📥 Entries

• in (Flow): Entry point triggering the web call (webhook or Zapier Push call).
• message (Number | Text | Boolean): Data or information to transfer to Zap (Zapier side automation). May contain username, score, game state, etc.

📤 Outings

• out (Flow): Exit point to continue execution of the flow after initiating network communication to Zapier.

💡 Example of use

Scenario: Notify an administrator on Slack when a player completes an Escape Game

1. The player solves the last puzzle of the game.
2. A variable Text is created to generate a dynamic message: User [Name] has just escaped in [Time] seconds!.
3. The flow arrives at the in input of the Zapier block.
4. The text variable containing the message is connected to the message input.
5. On the Zapier side, a preconfigured Zap is triggered via the Celestory integration and sends the message to a Slack channel or an email.
6. The administrator is immediately notified, while the end screen ("Well done!") is displayed normally using the out output.

⚙️ Technical Details

• Technical operation: the block sends a request over the Internet (called a "webhook"); the value sent is always converted to text, even if it started out as a number or a boolean (true/false).
• System requirements: for this block to work, your Celestory account must be linked to a Zapier account.

🔗 See also

• Make: equivalent for the Make platform (formerly Integromat).
• Voltask Webhook: optimized alternative for the Celestory-Voltask ecosystem.
• HTTP Request: to call an API directly without going through Zapier.

Documented version: v1

Updated on: 06/09/2026