> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sagescreen.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Build a Breakcold ``task.created``-shaped payload and POST it to the

> Build a Breakcold ``task.created``-shaped payload and POST it to the
    fixed Zapier catch-hook. Breakcold itself is never called.

    Called by ``triage-bc`` right after ``tasks_create`` so the downstream
    Zapier flow (enrichment, Akiflow twin, Notion tracking page) runs. The
    routine's own sandbox cannot reach Zapier directly; this server can.

    record_id:    the Breakcold CRM record id the task is linked to
    task_id:      the new Breakcold task id, from ``tasks_create``'s response
    title:        the task title
    workspace_id: the Breakcold workspace id (from ``workspaces_list``)
    due_at:       the due date just set on the task, ISO 8601

    Returns a JSON string:

      * ``{"status": "ok"}`` when Zapier accepted (2xx)
      * ``{"status": "error", "error": "..."}`` on validation failure or
        Zapier error. Never includes the catch-hook URL's secret path beyond
        what is already fixed in this module.



## OpenAPI

````yaml /openapi/private/specs/mcp/sagescreen.yml post /tools/relay_bc_task_created
openapi: 3.1.0
info:
  title: SageScreen — MCP Tool Catalog
  description: >-
    Agent-callable tools exposed by the SageScreen MCP server at
    `https://mcp.sagescreen.net`.


    These are the same tools served over the Model Context Protocol; this
    reference documents their **REST** surface (`POST /tools/{name}`, body = the
    tool's arguments), which is what the playground below invokes. The live,
    machine-readable catalog is `GET /tools/list`.


    **This page is generated deterministically** from the server's tool registry
    (`apps/docs/scripts/generate_mcp_spec.py`), not hand-written and not
    AI-generated — it cannot drift from the shipped tools.


    All calls authenticate with the `X-Service-Token` header (or `?token=`).
  version: 1.0.0
servers:
  - url: https://mcp.sagescreen.net
    description: Production MCP server
security:
  - serviceToken: []
  - tokenQuery: []
tags:
  - name: Agents
  - name: Contact Push
  - name: Image Generation
  - name: Other
  - name: Productlane
  - name: Reply.io
  - name: Sequences
  - name: Spaces
  - name: WordPress
paths:
  /tools/relay_bc_task_created:
    post:
      tags:
        - Other
      summary: Build a Breakcold ``task.created``-shaped payload and POST it to the
      description: |-
        Build a Breakcold ``task.created``-shaped payload and POST it to the
            fixed Zapier catch-hook. Breakcold itself is never called.

            Called by ``triage-bc`` right after ``tasks_create`` so the downstream
            Zapier flow (enrichment, Akiflow twin, Notion tracking page) runs. The
            routine's own sandbox cannot reach Zapier directly; this server can.

            record_id:    the Breakcold CRM record id the task is linked to
            task_id:      the new Breakcold task id, from ``tasks_create``'s response
            title:        the task title
            workspace_id: the Breakcold workspace id (from ``workspaces_list``)
            due_at:       the due date just set on the task, ISO 8601

            Returns a JSON string:

              * ``{"status": "ok"}`` when Zapier accepted (2xx)
              * ``{"status": "error", "error": "..."}`` on validation failure or
                Zapier error. Never includes the catch-hook URL's secret path beyond
                what is already fixed in this module.
      operationId: relay_bc_task_created
      requestBody:
        required: true
        content:
          application/json:
            schema:
              properties:
                record_id:
                  title: Record Id
                  type: string
                task_id:
                  title: Task Id
                  type: string
                title:
                  title: Title
                  type: string
                workspace_id:
                  title: Workspace Id
                  type: string
                due_at:
                  title: Due At
                  type: string
              required:
                - record_id
                - task_id
                - title
                - workspace_id
                - due_at
              type: object
      responses:
        '200':
          description: >-
            Tool result. The shape is tool-specific; most tools return a JSON
            object, some a `{"result": ...}` envelope.
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
        '400':
          description: Bad arguments (unknown kwargs, malformed JSON body).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          description: Unknown tool name.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: Tool raised an error during execution.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    ErrorResponse:
      type: object
      properties:
        error:
          type: string
          description: Human-readable error message.
        detail:
          type: string
          description: Optional additional context.
      required:
        - error
  responses:
    Unauthorized:
      description: Missing or invalid service token.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            error: Unauthorized
  securitySchemes:
    serviceToken:
      type: apiKey
      in: header
      name: X-Service-Token
    tokenQuery:
      type: apiKey
      in: query
      name: token

````