Initiate your Jsonify workflows via an HTTP POST request, allowing integration with any external system capable of sending webhooks.
Start on incoming webhook
block acts as a trigger, enabling your Jsonify workflow to be started programmatically by an external system via an HTTP POST request. This provides immense flexibility for integrating Jsonify into larger automation pipelines or custom applications.
When this trigger is configured, Jsonify provides a unique URL. Sending a POST request to this URL will initiate the workflow. You can also pass parameters in the body of the POST request, which can then be used as variables within your Jsonify workflow.
Start on incoming webhook
trigger block to:
Timer
.
https://app.jsonify.com/api/v2/workflow/YOUR_WORKFLOW_ID/node/YOUR_NODE_ID/start
).curl
command provided in the UI shows an important header: -H "Authorization: Bearer YOUR_API_KEY"
.You must include this Authorization header
with a valid Jsonify API key in your POST request.{{variable_name}}
syntax.
Example curl with a JSON body to pass parameters:
{{input_url}}
, {{search_query}}
, and {{user_id}}
.
Screenshot: Start on incoming webhook block configuration panel showing the Webhook URL and example curl command
Start on incoming webhook
trigger in your Jsonify workflow. This generates a unique URL and requires an API key for authorization.Authorization: Bearer YOUR_API_KEY
header.{"url_to_process": "USER_SUBMITTED_URL"}
.Start on incoming webhook
.Open Websites
, configured with its URL field set to {{url_to_process}}
.Content-Type
header is set to application/json
.Start on incoming webhook
block provides a powerful and flexible method for integrating Jsonify into a wide array of custom systems and external event sources.