Auto-map a goal to an outbound trigger binding (the AI assistant)
Given a natural-language GOAL, an LLM proposes the event-leaf → intent-var mapping over the trigger’s declared output fields; the proposal is VALIDATED by the compiler (with one self-correct retry) and created as a DISABLED trigger for review. 503 if no LLM is configured; 422 if a valid mapping couldn’t be produced; 409 if not connected. Use this when you’d rather describe the goal than hand-map fields. To specify the event→field bindings explicitly, use createOutboundTrigger (POST …/triggers) instead. Either way the trigger lands DISABLED for your review before it can dial.
Authorizations
Flowyte secret API key (Authorization: Bearer flowyte_sk_live_…). Scope-gated; is scoped to your organization — a key can never reach another tenant. The listed scopes in each operation's apiKey requirement are the scopes that key must hold. The tokenUrl is nominal: keys are minted in the dashboard.
Path Parameters
The agent this resource is scoped to (the UUID returned by createAgent / listAgents).
The integration provider (connector). One of the supported connector slugs: native providers (google_calendar, google_sheets, calendly, hubspot, ``, square, opentable, shopify), SQL databases (postgres, mysql), the universal Zapier MCP fallback (zapier), or Composio (composio).
google_calendar, google_sheets, calendly, hubspot, square, opentable, shopify, postgres, mysql, zapier, composio Body
A natural-language description of the recipient/data to call about.
pewc, express, ebr, none consumer, business Response
The compiled (disabled) trigger.
A compiled outbound trigger ("when {event} in {provider} → call {agent}"). The server-authored fields (agentId, callerNumberId, messageCategory, intentType, consentBasis) are PINNED at compile; the inbound payload can never choose them. It lands disabled and the operator enables it (a standing consent attestation).