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

# Marketing Execution Flow: From Intent to Source-System Write

> The fifteen-step execution path for Marketing actions: how an intent like budget adjustment becomes a governed, receipted write to HubSpot with full audit.

The Marketing execution flow turns your intent into a governed, receipted action. Whether you are adjusting campaign spend, publishing a content asset, or updating a nurture sequence, the same pipeline runs: intent is captured, context resolved, a proposal built, and the action writes back with proof.

<Steps>
  <Step title="Intent">
    You choose an action, such as pausing a campaign or updating a lead nurture sequence.
  </Step>

  <Step title="Context">
    Spine resolves the current campaign graph, permissions, and guardrails relevant to the intent.
  </Step>

  <Step title="Decision">
    Twin or the domain agent confirms the action is valid and suggests prerequisites.
  </Step>

  <Step title="Proposal">
    A capability proposal is generated: what will change, in which system, and the expected outcome.
  </Step>

  <Step title="Capability Resolution">
    Spine selects the correct capability, such as `campaign.ad_spend.adjust`, and checks authorization.
  </Step>

  <Step title="Handoff">
    If approval is required, the proposal routes to a manager or compliance agent.
  </Step>

  <Step title="Tool Selection">
    Spine picks the connector: HubSpot API, Marketo API, or Salesforce API.
  </Step>

  <Step title="MCP/Connector">
    The connector translates the capability into the target system's native API call.
  </Step>

  <Step title="Authorization">
    OAuth tokens or API keys are injected. The call is signed and scoped to the user.
  </Step>

  <Step title="Human Approval">
    For high-impact actions, a final approval panel shows diff and impact summary.
  </Step>

  <Step title="Workflow Execution">
    The API call is executed. Spine waits for confirmation and handles retries.
  </Step>

  <Step title="Source-System Write">
    HubSpot, Marketo, or Salesforce records update. Dependent triggers may fire in the source system.
  </Step>

  <Step title="Receipt">
    Spine generates a receipt: actor, timestamp, input, output, and sync status.
  </Step>

  <Step title="Event">
    A domain event is emitted. Views refresh, agents observe, and continuity tokens update.
  </Step>

  <Step title="Continuation">
    Your session context and campaign graph are updated. Twin monitors for the next trigger.
  </Step>
</Steps>

## Related

* [Capabilities](/internal-docs/domains/marketing/capabilities)
* [Workflows](/internal-docs/domains/marketing/workflows)
* [System Flow](/internal-docs/domains/marketing/system-flow)
* [Governed Actions](/how-it-works/governed-actions)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.