Make (formerly Integromat) is a visual automation builder. If your team uses it to wire up Typeform, Stripe, Airtable, or any of the other ~2000 apps it supports, you can drop K3X into the same scenarios with one HTTP module.
Two directions to know.
Make → K3X. A Make scenario POSTs to your K3X Agent's webhook URL. Use Make's HTTP “Make a request” module. This is the pattern most teams set up first.
K3X → Make. K3X POSTs to a Make scenario when something happens in your CRM. Make uses its built-in Custom webhook module as the trigger.
Worked example: Typeform submission becomes a K3X lead.
You have a "Get a demo" Typeform on your marketing site. You want every submission to land in K3X as a lead, get assigned to a rep, and trigger an Agent that drafts a welcome email.
Step 1 — Build the Agent in K3X.
In K3X, go to /agents/new and tell the chat builder what you want: "When a new demo request comes in via webhook, create a lead with the form data, assign it round-robin to the sales team, and draft a welcome email for me to review." Switch on the Webhook trigger. Copy the webhook URL the Agent gives you — something like https://api.k3x.ai/v1/agents/agt_8f4a2/webhook. While you're there, generate a signing secret if you want to lock the endpoint down.
Step 2 — Start a new Make scenario.
In Make, click Create a new scenario. Add Typeform → Watch responses as the trigger module, pick the form, and run the trigger once so Make captures a sample submission. You should see the form fields (name, email, company, etc.) in the module's output.
Step 3 — POST to K3X.
Add a second module: HTTP → Make a request. Configure it:
URL: paste the Agent's webhook URL from Step 1
Method: POST
Body type: Raw, Content type: JSON (application/json)
Request content: a JSON object that maps Typeform fields to whatever your Agent's prompt expects. Drag Typeform output into the JSON body using Make's variable picker. For example:
{
"source": "typeform-demo-request",
"name": "{{1.answers.name}}",
"email": "{{1.answers.email}}",
"company": "{{1.answers.company}}",
"notes": "{{1.answers.what_brings_you_here}}"
}If you set a signing secret, add a header: X-K3X-Signature with an HMAC-SHA256 of the body. Make has a sha256 function under the Cryptographic group for this.
Step 4 — Test, then turn the scenario on.
Click Run once in Make. Submit a real (or fake) Typeform entry. Check the HTTP module output — you want a 200 back from K3X. Then jump to K3X and confirm the Agent fired and the lead is sitting in your pipeline. If both look right, flip the scenario to ON and you're live.
Going the other way: K3X → Make.
Same shape, mirrored. In Make, start a new scenario with the Webhooks → Custom webhook trigger. Make generates a URL like https://hook.eu2.make.com/abc123…. Copy it. In K3X, open the Agent and add an outbound webhook action: pick the event (e.g. "lead qualified"), paste the Make URL. Trigger the event once so Make captures a sample payload and learns the schema. Then build out the rest of your Make scenario — send a Slack message, append a row to Google Sheets, whatever you need.
Recipes to try.
Stripe → K3X. When a Stripe customer is created, POST to a K3X Agent that creates or updates the matching lead and tags it as a paying customer.
Calendly → K3X. When a meeting is booked, POST to a K3X Agent that logs the meeting on the right lead and drafts a pre-meeting research note.
K3X → Slack. When an Agent qualifies a lead above $50K ARR, POST to Make, which posts a formatted message in your #wins channel.
K3X → Google Sheets. When a deal closes won, POST to Make, which appends a row to your finance team's revenue tracker.
Troubleshooting.
K3X returns 401. Your signing secret doesn't match. Re-generate it in K3X and update the Make HTTP module's signature header.
K3X returns 422. The JSON body is malformed or missing fields the Agent expected. Open the HTTP module's request preview in Make and check the actual body it sent.
Scenario doesn't fire. Confirm the Make scenario is ON, not just saved. Custom webhook URLs only receive when the scenario is active.
Make scenario fired but K3X didn't react. Check the Agent's runs list in K3X — if you see no run, the request never arrived; if you see a failed run, the Agent ran but errored on something inside the prompt.
Next: Connect K3X with Zapier →