Paste whatever the partner sent you and get the integration filled in. What it does, what it never touches, and what you must check.
Building a template by hand means reading a partner's API docs and copying values into about twenty fields. AI draft does that reading for you: paste what the partner sent, press the button, and the form comes back filled in for you to review. It is included with your licence — there is nothing to configure or connect.
The most common reason a draft comes back half-empty is that too little was pasted. It reads only what is in the box — it cannot open links, log into a partner portal or guess at a page you didn't include.
So paste everything you were given, in one go: the send/registration endpoint, the status or deposit endpoint, the list of call statuses, and any example replies. A whole documentation page, a Postman export or a raw cURL dump all work — you do not need to tidy them up first, and you do not need to understand which parts matter. That is the job it is doing for you.
One thing worth knowing: partners almost always document the send endpoint at the top and the status/deposit endpoints much further down. If you copy only the first screen, you get a template that delivers leads but never pulls statuses back.
A draft — never a saved integration. Nothing is written until you press Apply and then Save, and no traffic reaches it until you attach its campaign to a flow. You get the transport, the auth method, the field mapping, the response paths, and, when the docs describe them, the status pull and the status mapping.
Anything it could not determine is listed under “Please provide”. That list is not a failure: it is the honest set of things only the partner can tell you — an affiliate id they assign, an undocumented response format, a status list that wasn't in the page. Treat it as your to-do list before going live.
API keys, tokens and passwords are deliberately left out, even when the partner's examples show real-looking values. The draft names the header or field the secret goes into; you paste the actual value on the Partner's page afterwards. That is what keeps one template shareable across many partners — the recipe is common, the credentials are not.
The draft is a fast first pass by something that read your text, not a verified integration. When the CRM says the draft is valid, that means the structure passed our checks — not that the values match your partner's docs. A wrong path does not throw an error; it fails quietly once real traffic runs. Go through it against the docs:
Then press “Send a test”. It runs one probe lead through the real config and shows you the request, the partner's raw reply and what was parsed out of it. Two minutes there is worth more than any amount of re-reading.
Drafting is metered per licence — a handful per minute and a daily allowance, which exists so one stuck loop cannot spend the shared budget. A normal integration takes two to five drafts, so you are unlikely to notice the limit. If you hit it, the message says so plainly and the allowance resets at midnight UTC.
If a partner's API does something genuinely unusual, send us their docs — we'll help you map it.