🟪 Voltask Webhook

The Voltask Webhook block allows you to create a direct technological bridge between Celestory and Voltask by sending HTTP requests to this external system to trigger back-end actions without implementing a Parameterized HTTP Requests block.
This block is ideal for automating complex workflows and triggering powerful actions in the background, without burdening the user experience.

📥 Entries

• webhook (Text/Identifier): Unique URL or identifier pointing to the targeted Voltask workflow. Essential to direct the request to the correct endpoint.
• payload (JSON/Data Object): Packet of information to transmit (variables, scores, user data). Example: {"name": V_Player_Name, "score": V_Player_Score}.

📤 Outings

• response (JSON/Text): Return from the remote server if the webhook is bidirectional. Contains the result of the operation (eg: "Validated OK!").
• stream_de_flux (Signal): Asynchronous signal indicating that sending has been attempted or completed, regardless of possible errors (timeout, etc.).

💡 Example of use

Scenario: Transmission of data from a customer quiz to Voltask

1. A user completes an interactive quiz in a Celestory application and enters their contact details (name, email, phone) via "Text entry" blocks.
2. The variables V_Name, V_Email and V_Telephone are stored in the flow.
3. The Voltask Webhook block is placed at the end of the route to transmit this data.
4. The payload is constructed with the variables: {"name": V_Name, "email": V_Email, "telephone": V_Telephone}.
5. The Voltask webhook URL (ex: https://api.voltask.com/webhook/12345) is entered in the webhook entry.
6. On validation, the block sends the data. Voltask receives the payload and automatically triggers a workflow (e.g. sending a confirmation email or updating a database).

⚙️ Technical Details

• Performance optimization: Unlike tools like Zapier or Make, this block is optimized for the Celestory-Voltask ecosystem, reducing latency and simplifying integration without complex analysis.
• Error management: The stream_de_flux signal makes it possible to follow the status of the sending even in the event of failure (timeout, network error).

🔗 See also

• HTTP Request: for finer control (method, body, content type) over a one-off API call.
• Zapier / Make: for multi-step automations on the third-party platform side.

Updated on: 29/07/2026