Third-Party Integration Lead

What it does

Third-Party Integration Lead is a Cursor agent playbook named integration-engineer. AgenticKit installs it so a session can adopt this role instead of acting as a generic coding assistant.

The integration-engineer agent seamlessly bridges your SaaS with third-party ecosystems. It implements OAuth 2.0 PKCE authentication, robust Stripe webhook event handlers, transactional email templates, and bi-directional CRM syncing.

Connects webhooks, OAuth protocols, Stripe payments, Resend email, and CRMs. Integration engineer for Cursor specializing in OAuth flows, Stripe billing, Resend transactional emails, GitHub APIs, and CRM synchronizations.

Why it exists

A pile of agent files is not a team. integration-engineer exists so one job, third-party integration lead, has a written brief, required skills, and a stop condition.

It ships in the Engineering Kit. Skills it must read: OAuth 2.0 & Third-Party API Integrations; Stripe Subscriptions & Webhook Handling; REST & API Route Design Patterns. Commands that adopt this role: /stripe-billing: Stripe Billing & Subscription Setup; /auth-system: Authentication & Role-Based Access System; /build-api: API Endpoint & Route Generator.

When to use it

• Building Google/GitHub OAuth login systems
• Setting up end-to-end Stripe subscription billing
• Connecting HubSpot, Slack, or Discord webhook notifications

When not to use it

• Do not ask integration-engineer to do a different role's job. If you need a launch post, switch agents.
• Do not keep the same chat after this agent has finished its artifact. Start a reviewer in a new thread.
• Do not invoke every agent in the kit for a small change.

Example workflow

1. Install the Engineering Kit so .cursor/agents/integration-engineer is on disk.
2. Run /stripe-billing: Stripe Billing & Subscription Setup, or start a chat and tell Cursor to adopt the integration-engineer role.
3. The agent should read: OAuth 2.0 & Third-Party API Integrations; Stripe Subscriptions & Webhook Handling; REST & API Route Design Patterns.
4. It produces the artifact for this role only, then stops.
5. A different agent or you review. Same-chat self-review is not a review.

Example usage

Example: "You are integration-engineer. Building Google/GitHub OAuth login systems. Read oauth-integrations before you edit."

Or let the pipeline invoke it: /stripe-billing: Stripe Billing & Subscription Setup.

Capabilities you should actually see: OAuth 2.0 and OpenID Connect authorization flows

Example output

• integration-engineer should leave files or a written verdict, not a vibe check. OAuth 2.0 and OpenID Connect authorization flows Stripe checkout, subscription lifecycle, and invoice webhooks
• Engineering agents should touch the slice they were given (schema, route, test, or review note) and nothing else.

Best practices

• OAuth 2.0 and OpenID Connect authorization flows
• Stripe checkout, subscription lifecycle, and invoice webhooks
• Resend and SendGrid transactional email integration
• Third-party API rate limit management and token refreshes
• One role per chat unless a command is explicitly orchestrating a sequence.

Common mistakes

• Using integration-engineer as a synonym for 'the Cursor agent'. It is a brief, not the product.
• Skipping the required skills and hoping the role name is enough.
• Letting the writer approve its own PR.
• Invoking this agent and three unrelated ones in the same prompt.