Lytics Integrations

Everything between "I want to connect X" and a running job: picking the provider and workflow, field mapping, auth credentials, connections to external data sources, webhook templates for custom destinations, the job lifecycle (create, update, pause, resume, bounce, kill, logs), and debugging why one user did or didn't reach a destination. Integrations are layered: Provider (what platform) -> Auth (how to authenticate) -> Connection (optional, for data-source integrations) -> Job (runs one workflow).

Before you start

• Credentials: references/auth.md.
• Request conventions, URL-encoding and the /v2 error shape (.errors[0].message): references/api.md.
• Every create, update, delete and lifecycle command goes through references/confirmation-gate.md (pause/resume may use a brief confirmation; kill needs explicit confirmation).
• Never log or display full credential values. OAuth cannot be completed from the CLI: send the user to the Lytics UI, then pick up the new auth_id via GET /v2/auth.

Gotchas