funnel

Call funnel.test_part

Prove ONE configured part of a funnel — 'test the landing page', 'check the first email sends' — by running a synthetic test lead through it — a form fill that has to land a lead, a first send that has to reach the test inbox. The lead is always synthetic and every send goes to the workspace's designated test address, never a real person. It writes passed, or failed naming the exact step, onto the funnel's plan. A part that has not passed is unverified, never done — and the funnel AS A WHOLE stays unverified however many parts pass. Not for the whole funnel end to end — that is funnel.test_end_to_end. 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.test_part

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/funnel.test_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 to prove. It has to have been configured 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 4 revisions of this API.