instantly-core-workflow-b

Instantly Sending Account Onboarding

Overview

Onboard Google or Microsoft sending accounts without exposing credentials or assigning unhealthy accounts to live campaigns. Record assumptions, evidence, approval state, and rollback ownership so another operator can reproduce the result.

Prerequisites

• The target repository, Instantly workspace, environment, and accountable owner
• Current security, privacy, compliance, capacity, and change-control requirements
• An approved API v2 key only when a bounded live verification is necessary

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current first-party Instantly documentation and package metadata. Use Write or Edit only when implementation was requested and exact target files are known; never write credentials, lead data, email content, or unrestricted environment output.

Current Contract

• Google and Microsoft connections use an OAuth session URL followed by status polling.
• OAuth sessions expire after 10 minutes.
• Warmup enablement may return a background job that must be polled.

Authentication

Use an API v2 key as Authorization: Bearer <key> against https://api.instantly.ai/api/v2. Grant only the endpoint-specific scopes needed, inject the key from an approved server-side secret manager, and never print, persist, commit, or place it in a URL. Treat key creation, rotation, revocation, member changes, workspace delegation, and production access as owner-approved actions.

Instructions

1. Confirm account ownership, provider, workspace, allowed domains, and change owner.
2. Create a least-privilege OAuth session and give the authorization URL only to the account owner.
3. Poll the session within its expiry window without logging tokens.
4. Test account vitals and capture only non-sensitive status fields.
5. Enable warmup or campaign assignment only after an explicit change approval.
6. Poll background jobs and produce per-account success and failure evidence.

Approval Boundaries

Do not create, rotate, reveal, or revoke keys; invite or remove members; delegate across workspaces; connect sending accounts; create or activate campaigns; import or delete leads; change suppression or retention; register, patch, resume, or delete webhooks; alter plans or paid capacity; transmit diagnostics; or perform another production mutation without explicit approval from the accountable owner. Keep diagnosis read-only unless implementation was requested.

Output

Return the workspace-safe scope, files and contracts inspected, exact API v2 routes and required scopes, evidence collected, validation result, sensitive fields redacted, remaining risk, accountable owner, approval state, and rollback or next action.

Error Handling

Examples

Use a compact handoff that makes scope, mutation authority, and evidence reviewable.

Input:

provider=google; accounts=3; assign-campaign=false

Expected handoff:

oauth=complete; vitals=3/3; mutation=awaiting-owner

Resources

• Skill-specific official documentation
• Instantly API v2 documentation
• Instantly API v2 OpenAPI document