Agent Handoffs
Generate safe Direct API implementation guidance for Codex, Cursor, Claude Code, or Markdown workflows.
Agent handoffs give a coding agent compact SaaSFunnels guidance without exposing real credentials. Use them when an agent will inspect a codebase and propose or implement account-scoped revenue events.
Generate handoff files
Generate Direct API implementation guidance for the coding tool you use:
saasfunnels agent install --target codex
saasfunnels agent install --target claude-code
saasfunnels agent install --target cursor
saasfunnels agent install --target markdownThe generated files use <SAASFUNNELS_INGEST_KEY> placeholders. They should help the agent find durable backend events, choose source boundaries, and avoid unsafe payloads without exposing real credentials.
What the handoff should guide
Ask the agent to look for:
- Backend events emitted after durable writes or provider confirmations.
- Stable account, workspace, tenant, company, or customer identifiers.
- Idempotency keys based on source event identity.
- Bounded event properties that explain revenue relevance.
- Existing PostHog or Segment events that already carry account identity.
- Web SDK moments that are browser-visible and safe.
What the handoff should avoid
Do not ask the agent to:
- Put Direct API ingest keys in browser, mobile, desktop, or public client code.
- Send raw provider payloads, tokens, auth headers, full URLs with query strings, invite links, prompts, comments, stack traces, or raw logs.
- Forward every analytics event.
- Invent campaign execution, CRM updates, or lifecycle actions that humans have not approved.
Pair with MCP
Use SaaSFunnels MCP Server when the agent should read SaaSFunnels semantics, source requirements, mapping gaps, readiness, or safe payload previews directly.
Use handoff files when the agent needs local project instructions that can be reviewed and versioned with the implementation work.