funnel

Call funnel.execute_part

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.

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

Headers

x-request-idstring

Your own id for this request, echoed back and recorded on the audit trail. 1–128 characters from A–Z a–z 0–9 . _ : -, starting with a letter or digit; anything else is replaced by a generated id.

Request body

project_board_idstring 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_namestring

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.

confirmation_idstring 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.

workspacestring

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

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.

OR

Changes

No recorded changes to this operation across all 5 revisions of this API.