> ## Documentation Index > Fetch the complete documentation index at: https://docs.anycrm.anyreach.ai/llms.txt > Use this file to discover all available pages before exploring further. # Push Outreach Drafts To Mailbox > Copy one step of each contact's Personal drafts into a mailbox's Drafts. The mailbox is the one the person connected themselves (Outlook or Gmail, via Connected accounts), so the drafts sit in their own Drafts folder and leave from their own address when they press Send. Nothing is sent here. * Step 1 becomes a new email to the contact. * A later step becomes a reply in the thread of the step-1 email, found in Sent by recipient and subject. Until that email has been sent the step is skipped (``earlier_step_not_sent``), never drafted unthreaded. * Each push is recorded on the contact's by-run entry (``mailbox_drafts``), so running it twice does not stack duplicates; ``force`` overrides. * Disqualified, opted-out and email-less contacts are skipped. ## OpenAPI ````yaml /openapi-generated.json post /customer-intelligence/outreach-drafts/push-to-mailbox openapi: 3.1.0 info: title: anycrm-api version: 0.0.1 servers: [] security: [] tags: - name: Customer Intelligence description: >- Company research and ICP-fit scoring — create a research run, track its progress, and read back scored companies as leads. - name: Outreach description: >- The cold-email sending infrastructure — domains and mailboxes, over Primeforge and Warmforge. - name: AnyCard description: >- Authenticated CRUD for AnyCard, the org's digital business-card / lead-capture product. - name: AnyCard Events description: >- Event-attribution analytics for AnyCard — which captured leads converted, broken down by source, owner, and deal. - name: AnyCard Share Links description: >- Unauthenticated endpoints reached by anyone who scans a QR code or opens a shared AnyCard link. - name: AI description: >- A streaming (SSE) AI chat endpoint with account-commit actions it can take on the caller's behalf, and the job that fills every deal and account tab of an org. - name: Analytics Assistant description: >- The natural-language analytics assistant — a guarded text-to-SQL loop (SSE) that answers ad-hoc questions over the org's CRM data as a least-privilege, read-only database role. - name: Account Readiness description: >- Account Readiness Profiles — AI-scored signals on whether an account is ready for outreach or expansion, computed via a Temporal workflow. - name: Integrations description: >- Pipedream Connect — issuing connect tokens and managing the org's connected third-party accounts. - name: Feedback description: >- User-submitted platform feedback (bug reports, feature requests) — global, not scoped to one organization. - name: Public Media description: >- Unauthenticated image reads for publicly-embeddable assets (card photos, inline email images) — allowlisted by key shape; everything else in the storage bucket stays private. - name: Service Health description: Service liveness. paths: /customer-intelligence/outreach-drafts/push-to-mailbox: post: tags: - Customer Intelligence summary: Push Outreach Drafts To Mailbox description: >- Copy one step of each contact's Personal drafts into a mailbox's Drafts. The mailbox is the one the person connected themselves (Outlook or Gmail, via Connected accounts), so the drafts sit in their own Drafts folder and leave from their own address when they press Send. Nothing is sent here. * Step 1 becomes a new email to the contact. * A later step becomes a reply in the thread of the step-1 email, found in Sent by recipient and subject. Until that email has been sent the step is skipped (``earlier_step_not_sent``), never drafted unthreaded. * Each push is recorded on the contact's by-run entry (``mailbox_drafts``), so running it twice does not stack duplicates; ``force`` overrides. * Disqualified, opted-out and email-less contacts are skipped. operationId: >- push_outreach_drafts_to_mailbox_customer_intelligence_outreach_drafts_push_to_mailbox_post requestBody: content: application/json: schema: $ref: '#/components/schemas/MailboxDraftsPushBody' required: true responses: '200': description: Successful Response content: application/json: schema: additionalProperties: true type: object title: >- Response Push Outreach Drafts To Mailbox Customer Intelligence Outreach Drafts Push To Mailbox Post '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' security: - HTTPBearer: [] components: schemas: MailboxDraftsPushBody: properties: run_ids: items: type: string type: array maxItems: 10 minItems: 1 title: Run Ids step: type: integer maximum: 12 minimum: 1 title: Step default: 1 contact_ids: anyOf: - items: type: string type: array maxItems: 500 - type: 'null' title: Contact Ids dry_run: type: boolean title: Dry Run default: false force: type: boolean title: Force default: false as_user_id: anyOf: - type: string maxLength: 64 - type: 'null' title: As User Id limit: type: integer maximum: 500 minimum: 1 title: Limit default: 200 signature: anyOf: - type: string maxLength: 1000 - type: 'null' title: Signature sender_first_name: anyOf: - type: string maxLength: 60 - type: 'null' title: Sender First Name type: object required: - run_ids title: MailboxDraftsPushBody description: >- Copy Personal drafts into a person's own Outlook / Gmail Drafts folder. For senders who write from their own mailbox rather than a campaign: the sequence step lands as a draft they read and send themselves. Nothing is sent. Step 1 is a new email; later steps are replies in the thread of the step-1 email the person already sent (skipped until it has been sent). HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location msg: type: string title: Message type: type: string title: Error Type type: object required: - loc - msg - type title: ValidationError securitySchemes: HTTPBearer: type: http scheme: bearer ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.