Webhooks
One webhook system for every integration
Every K3X agent works like a webhook — it receives external data, executes it instantly, and automatically maps every field into your workflows.
The webhook system
How the webhook system works
Data moves through four stages — from an external trigger to fully mapped execution inside your workflows.
External event
An external tool fires an event and sends its raw data to K3X.
Agent receives
Each agent acts as a live webhook endpoint, executing the payload.
Fields auto-map
All incoming fields are automatically mapped to your schema.
Workflow runs
Mapped data flows straight into your operations and triggers.
Automatic field mapping
Every field, mapped for you
The moment a payload arrives, K3X reads each incoming field and matches it to your schema — so raw external data becomes structured, usable records without any manual configuration.
Incoming payload
Mapped K3X field
user.email
Contact email
event.type
Trigger
created_at
Timestamp
payload.id
Record ID
team.name
Workspace
Agents as webhooks
What makes every agent a webhook
Executes external data
Any agent can receive and run incoming payloads as soon as they arrive, without manual oversight.
Maps every field
Source fields are automatically matched to your schema, so nothing is lost between systems.
Runs in your workflows
Mapped results flow straight into operations and trigger the next action across your stack.
FAQ
Integration questions answered
Learn how connections work, what is supported, and how external systems integrate.
Which integrations are available?
Standard integrations for email, SMS, and payments are included on every plan. Custom integrations are available on the Custom plan.
Is API access included?
Are custom integrations supported?
Do webhooks exist?