Custom connectors

Generate a connector with AI

From Platform → Pieces, choose Generate connector and paste a link to the API’s documentation. AgentFlow10 reads the documentation and drafts a connector — its actions, endpoints, parameters, and authentication — that you can review before publishing.

1. Documentation URL — a link to the API reference or an OpenAPI/Swagger specification.
2. Display name — optional; leave blank to let AI name it.
3. Additional instructions — optional guidance, e.g. “only include the contacts and deals endpoints.”
4. AI provider & model — pick a configured provider; leave the model on the provider default unless you have a preference.

The AI extracts the most useful operations and the primary authentication scheme. It only includes endpoints the documentation actually supports — it does not invent capabilities.

Review before publishing

Every generated connector is a draft. Before you publish, check:

• Base URL — the absolute URL that every action path is relative to.
• Authentication — the header, query parameter, or token scheme the API expects.
• Actions — each operation’s method, path, and inputs. Rename or remove anything you do not need.

Tips for better results

• Point at a focused endpoint reference rather than a high-level overview page; the more concrete the docs, the better the draft.
• If an OpenAPI specification is available, use it — structured specs produce the most accurate connectors.
• Use additional instructions to narrow a large API down to the operations your team actually uses.

A generated connector always gets an icon. If the documentation references a logo, that image is used; otherwise a favicon derived from the API’s domain is applied automatically.

Using your connector

Once published, a custom connector behaves like any built-in piece: it appears in the action picker, uses the connections you create for it, and can be shared across projects on plans that allow it.