⬜ Zapier

The Zapier block allows Celestory to be integrated with thousands of online tools via the Zapier no-code automation platform. It sends data or triggers events on external services (Airtable, Gmail, Slack, Discord, Google Sheets, etc.) directly from a Celestory graph.

This block is essential for transforming a narrative project into a connected application, capable of interacting with business tools or external workflows.

📥 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 acts as a network request (minimal Webhook) where the transmitted parameter is converted to text, regardless of its initial type (Number, Boolean, etc.).
• System requirements: The block must be connected to a Celestory account linked to Zapier to work.

Updated on: 04/03/2026