---
title: "Call funnel.execute_part"
method: POST
path: "/api/v1/tools/funnel.execute_part"
tags: ["funnel"]
---

# Call funnel.execute_part

`POST /api/v1/tools/funnel.execute_part`

## Request

- Base URL: `https://app.goosybear.ai`
- URL: `https://app.goosybear.ai/api/v1/tools/funnel.execute_part`
- Auth: HTTP bearer

Build ONE part of a funnel the member has already planned and scaffolded — 'build the landing page for the funnel', 'set up the email sequence for the funnel' — the landing page, the email sequence, and so on. Call it FIRST WITHOUT answers: it replies with the questions only the member can decide (the offer's numbers, the page's words, every email's copy) and creates absolutely nothing. Put those questions to them with ask_user — the run waits for their answer — then call it again with their answers, each copied word for word from their reply, and it drafts and configures the part through that part's own tools. An answer that is not in their own words is refused and asked again. A part whose prerequisites have not passed their test is refused, naming what is missing. Not for proving a built part with a test lead — that is `funnel.test_part`. Over the API it answers in two calls: without confirmation_id it proposes — says what would happen, returns a confirmation_id and changes, spends and sends nothing; the same arguments again with that confirmation_id, on a member's own API key, do it.

Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with `workspace_ambiguous` and lists the choices — offer them, never pick one.

## Headers

- `x-request-id` string

## Request body

- object
  - `project_board_id` string, uuid: The funnel's project id, if you have one from something you were shown. If you do not, use funnel_name instead — do not guess a uuid.
  - `funnel_name` string: What the member calls the funnel, when you do not have its id. It is matched against their own projects only.
  - `part` 'landing_pages' | 'email_sequences' | 'pipeline' | 'automations' | 'creative' | 'tracking' | 'data_table', required: Which part of the funnel to build. It must be one the plan covers, and every part it depends on must have PASSED its test first.
  - `answers` object[]: The member's answers to this part's leverage points. LEAVE IT OUT on your first call: the tool answers with the questions and creates nothing. Ask them with ask_user, then call again with their answers, each copied from their reply.
    - `leverage_point` string, required: The `id` of the leverage point being answered — copy it exactly from the question you were given. The question's own wording is accepted too; anything else is refused rather than guessed at.
    - `answer` string, required: What the MEMBER said, copied word for word from their answer. An answer that is not in their own message is refused and asked again — never your own draft standing in for their decision.
  - `confirmation_id` string, uuid: Omit to propose: the first call says what would happen, returns a confirmation_id and changes nothing. To go ahead, send the same arguments again with that confirmation_id, on a member's own API key; a service account's key can propose but never confirm.
  - `workspace` string: Which workspace to run in — its slug. Omit to use your default. With more than one reachable workspace and no default, the call is refused and the choices are listed.

## Response `200`

The call was admitted and dispatched. `ok` says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.

- union
  - object: The tool ran and answered.
    - `ok` true, required
    - `state` 'confirmation_required'
    - `confirmation_id` string, uuid
    - `expires_in_seconds` integer
    - `request_summary` string: What will happen, in one sentence, for a person to approve before confirming.
    - `project_board_id` string
    - `part` string
    - `label` string
    - `phase` 'awaiting_answers' | 'configured' | 'awaiting_confirmation'
    - `leverage_questions` object[]
      - `id` string, required
      - `question` string, required
    - `next_call` object
      - `tool` string, required
      - `input` object, required
    - `steps_run` object[]
      - `description` string, required
      - `tool` string, required
      - `ok` boolean, required
      - `detail` string, required
    - `status` 'unverified' | 'passed' | 'failed'
    - `answer_note` string
    - `workspace` string, required: The slug of the workspace this call ran in.
    - `working_in` object, required: Which workspace this call ran in, and how that was decided. Present on every workspace-scoped result.
      - `label` string, required: The chip words — e.g. "working in: Acme Main".
      - `note` string, required: Why this workspace — e.g. "your default", "this call only".
      - `workspace` string, required: The resolved workspace's slug.
      - `source` 'call-override' | 'key-pin' | 'stored-default' | 'sole-reachable', required: Which rung of the R7 precedence resolved the workspace.
  - ToolRefusal: A call that was admitted and dispatched, and did not succeed.
    - `ok` false, required
    - `code` string, required: The typed reason — e.g. `workspace_ambiguous`, `invalid_arguments`, or the tool's own failure code.
    - `message` string, required: A sentence a person can act on.
    - `workspaces` string[]: On a workspace refusal: the slugs this key may pass as `workspace`.
    - `issues` object[]: On `invalid_arguments`: which fields failed, and why.
      - `path` string, required
      - `message` string, required
    - `path` string: On an authoring refusal: where in your call's input it points, e.g. `steps.<key>.params.<field>`.
    - `fix` string: On an authoring refusal: the change to your call that would pass.
    - `instruction` string: On an authoring refusal: what to do next with it.

## Other responses

- `400`: The request could not be used: the body is present but not a JSON object (`tenant_api.malformed_body`); it is a top-level array carrying more messages than this endpoint accepts (`tenant_mcp.batch_too_large`); or the `Idempotency-Key` header is malformed (`tenant_api.idempotency_key_invalid`), disagrees with the body's `idempotency_key` (`tenant_api.idempotency_key_conflict`), or was sent to an action that cannot replay a retry (`tenant_api.idempotency_unsupported`). Nothing ran.
- `401`: No bearer credential, or one that did not resolve. Deliberately ONE undifferentiated answer for absent / unknown / revoked / expired, so the endpoint is never an oracle over the key space.
- `403`: The credential is good but the surface is not open to it — the platform or account API switch is off, or the holder lacks the `api.access` capability. The `code` says which.
- `404`: No such tool. The body names no tool and is identical for every unrecognised name.
- `429`: Over this key's per-minute cap. Carries `Retry-After` and `error.retry_after_seconds`.

---

[API](https://skmtc.dev/goosybear/apis/goosy-bear-api.md) · [All operations](https://skmtc.dev/goosybear/apis/goosy-bear-api/llms.txt) · [OpenAPI document](https://skmtc.dev/goosybear/apis/goosy-bear-api/revisions/6d82fb124064?raw)