n8n is open-source workflow automation, available as n8n Cloud or self-hosted. K3X connects with two stock nodes: HTTP Request to send data to an agent, Webhook to receive what an agent pushes out.
For n8n → K3X, your instance only needs outbound access to api.k3x.ai. For K3X → n8n, the Webhook node's URL must be reachable on the public internet over HTTPS. If n8n sits behind a firewall, expose it through a reverse proxy with TLS or a tunnel such as Cloudflare Tunnel.
Open the Agents tab and click Create Agent.
Describe it: "When a payment arrives by webhook, find the company by the customer's email domain, move its open deal to Plan Upgraded, add a note with the amount, and draft an onboarding email for review."
Add Webhook as a trigger and activate the agent.
Open the Webhook tab and copy the URL.
Create a workflow and add a Stripe Trigger node for charge.succeeded. Click Listen for Test Event and make a test charge so n8n captures a sample payload.
Add an HTTP Request node after the trigger.
Method: POST. URL: the agent's webhook URL.
Send Body: on. Body Content Type: JSON. Specify Body: Using Fields Below.
Add fields with simple names: source = stripe, email = {{ $json.billing_details.email }}, amount = {{ $json.amount }}, currency = {{ $json.currency }}, stripe_id = {{ $json.id }}.
Click Execute Workflow. The HTTP Request node should show a successful response. In K3X, open the agent's Activity tab to confirm the run and check the deal on the Pipelines board. Switch the workflow to Active. Until you do, live Stripe events will not reach it.
Add a Webhook node as the trigger of a new workflow. It exposes two URLs:
Test URL (/webhook-test/…): responds only while you have clicked Listen for Test Event. Use it to capture a sample.
Production URL (/webhook/…): responds whenever the workflow is Active. Use it for live events.
In K3X, open the agent and add a step: "Send a webhook to <Test URL> with the company name, website, deal stage and summary."
Click Listen in n8n, run the agent once, and n8n learns the fields.
Swap the step to the Production URL, build the rest of the workflow and activate it.
The agent's Deliveries tab shows each delivery and its status.
Webflow → K3X: form submission posts to an agent that creates the company and tags the campaign source in a custom field.
Postgres → K3X: a nightly n8n schedule queries trial signups and posts each one to an agent that creates the company and person.
K3X → Slack: an agent that spots a stalled deal pushes to n8n, which posts to the owner's channel.
K3X → warehouse: push every deal stage change to n8n and insert it into BigQuery or Snowflake.
No run in K3X: check the URL and that the workflow is Active, not only saved.
Run failed: open the run in Activity and compare field names with the HTTP Request node's output.
Production webhook not firing: confirm the agent step uses the production URL (no /webhook-test/) and the workflow is Active.
Self-hosted unreachable: K3X cannot call into a private network. Use a tunnel or a public reverse proxy.
Webhooks in K3X: the basics
Connect K3X with Make.com
Connect K3X with Zapier
