> ## 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. # Edit Result Outreach Drafts > Hand-edit one stakeholder's sequence, in both places it is stored. Synchronous rather than queued behind the revise workflow: there is no artifact to re-render, so a queued edit would leave a `pending` status nothing clears. Two single-table writes under the caller's org-scoped token. The contact is written FIRST — it is the copy a campaign sends from. A failed result write then leaves a stale report (a display defect); the reverse would send the old email. The step set is fixed: rewrite what a draft says, not how many there are. ## OpenAPI ````yaml /openapi-generated.json patch /customer-intelligence/runs/{run_id}/results/{result_id}/outreach-drafts 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 management console — domains, mailboxes, and campaigns — as a thin control plane over the SalesForge stack. - 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. - 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/runs/{run_id}/results/{result_id}/outreach-drafts: patch: tags: - Customer Intelligence summary: Edit Result Outreach Drafts description: >- Hand-edit one stakeholder's sequence, in both places it is stored. Synchronous rather than queued behind the revise workflow: there is no artifact to re-render, so a queued edit would leave a `pending` status nothing clears. Two single-table writes under the caller's org-scoped token. The contact is written FIRST — it is the copy a campaign sends from. A failed result write then leaves a stale report (a display defect); the reverse would send the old email. The step set is fixed: rewrite what a draft says, not how many there are. operationId: >- edit_result_outreach_drafts_customer_intelligence_runs__run_id__results__result_id__outreach_drafts_patch parameters: - name: run_id in: path required: true schema: type: string title: Run Id - name: result_id in: path required: true schema: type: string title: Result Id requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/OutreachDraftsEditBody' responses: '200': description: Successful Response content: application/json: schema: type: object additionalProperties: true title: >- Response Edit Result Outreach Drafts Customer Intelligence Runs Run Id Results Result Id Outreach Drafts Patch '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' security: - HTTPBearer: [] components: schemas: OutreachDraftsEditBody: properties: contact_id: type: string maxLength: 64 minLength: 1 title: Contact Id emails: items: $ref: '#/components/schemas/OutreachDraftEmail' type: array maxItems: 12 minItems: 1 title: Emails type: object required: - contact_id - emails title: OutreachDraftsEditBody description: >- Hand-edit one stakeholder's outreach sequence. Scoped to a person because that is how the drafts are stored, sent and read: a sequence belongs to a contact, and a campaign enrolls contacts. Editing the whole company at once would make every save a write to every contact row. Not a deliverable part — there is no artifact to re-render — so unlike ``DeliverableEditBody`` this is applied synchronously rather than queued behind the revise workflow, which would leave a `pending` status nothing ever clears. HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError OutreachDraftEmail: properties: step: type: integer maximum: 12 minimum: 1 title: Step subject: type: string maxLength: 300 minLength: 1 title: Subject body: type: string maxLength: 8000 minLength: 1 title: Body type: object required: - step - subject - body title: OutreachDraftEmail description: One hand-edited draft in a stakeholder's sequence. 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 ````