email_seed

Call email_seed.push

Hand a finished sequence over to the member's connected marketing tool to send — 'push this into my CRM', 'send it over to my email tool', 'load this sequence into GHL'. Hand a finished sequence to the customer's connected marketing tool, which then owns the sending. This writes into an outside system, so calling it raises the approval card, which is the operator's confirmation; call it on the ask, and it hands the sequence over only once they approve. It does not send email itself. Not for recording that they copied it out by hand — that is email_seed.record_export. 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/email_seed.push

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/email_seed.push
  • 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

board_idstring uuid required

The finished sequence to hand off.

mode_keystring required

Which hand-off ending the operator chose. Use a key the seed sheet offered — the server resolves it against its own catalogue and refuses anything else.

audience_keystring nullable required

The connected tool's audience/list key, or null when the chosen ending needs none. It is re-read from the provider, never trusted.

start_datestring nullable required

The first send date as YYYY-MM-DD, or null when the ending needs none.

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 6 revisions of this API.