Who This Is For / When to Use
Use the Inbound Webhook trigger if you need to:
Send real-time data from external systems into Kyrios
Trigger workflows from purchases, events, or third-party apps
Run workflows with or without contact data
Map external payload data to workflow actions
What the Inbound Webhook Trigger Does
The Inbound Webhook trigger listens for incoming HTTP requests and starts a workflow when data is received.
Supports POST, GET, and PUT
Accepts JSON payloads only
Can run contactless or create/update contacts
Exposes incoming fields as custom values inside workflows
This is a premium trigger and incurs additional execution charges.
Step 1: Add the Inbound Webhook Trigger
Go to Automations > Workflows.
Create a new workflow or open an existing one.
Click Add New Trigger.
Select Inbound Webhook.
Step 2: Copy the Webhook URL
After selecting the trigger:
Copy the generated Webhook URL.
Use this URL in your external system.
Choose a supported method: POST, GET, or PUT.
Important:
Maximum payload size: 1 MB
Only JSON payloads are supported
Step 3: Send a Test Request
From your external system (or a tool like Postman):
Send a JSON request to the webhook URL.
Confirm a 201 Created response.
Copy the returned request ID.
Step 4: Fetch and Select the Mapping Reference
Return to the Inbound Webhook trigger.
Click Fetch Sample Requests.
Locate the request using the copied ID.
Select the reference to load its payload structure.
Note:
The most recent request always appears at the top.
Step 5: Verify the Incoming Payload
Confirm the payload structure matches what your workflow expects.
Step 6: Map Data in Create / Update Contact (Optional)
After saving the trigger, Kyrios opens the Create / Update Contact action.
Select contact fields (Email or Phone is required).
Map incoming webhook values to fields.
Save the action.
Requirement:
To create or update a contact, Email or Phone must be included in the payload.
Using Webhook Data in Other Actions
Inbound Webhook values appear as custom values and can be used in:
Email
SMS
Slack
If / Else conditions
Google Sheets
Internal tools
Using Webhook Data in If / Else Conditions
Webhook fields can drive branching logic.
Example:
Contactless Workflow Execution
Inbound Webhook workflows do not require contact data.
You can:
Send payload data only
Skip contact creation
Run actions like Slack, Google Sheets, Custom Webhooks, or internal tools
Example use case:
Send order data → evaluate value → notify Slack → log to Google Sheets
Important Rules and Limitations
Only JSON format is supported
Keys must not contain spaces
Usesnake_caseorcamelCaseArrays cannot be used as custom values
If payload structure changes, re-select the mapping reference
If the webhook URL is compromised:
Delete the trigger
Create a new Inbound Webhook trigger
Update external systems with the new URL
FAQs
What is an Inbound Webhook?
A trigger that starts a workflow when external systems send data to Kyrios.
Which HTTP methods are supported?
POST, GET, and PUT.
Do I have to create a contact?
No. Workflows can run without contact data.
What is required to create or update a contact?
An Email or Phone field must be present.
Can I use webhook data in all workflow actions?
Yes. Values are available as custom values across actions.