Codex
Claude
GeminiWhat you do
- Choose one supported CRM object type, exact safe property refs, format, and retention policy.
- Review data scope and approve creation of the provider export job.
- Receive either the completed artifact or a safe pending/repair handoff.
Revenue operations teams requesting bounded HubSpot CRM data exports / gtm
GTM CRM Export Handoff
One approved bounded export with a safe job ref, a retained StackOS artifact when complete, and truthful pending, partial, or failed evidence.
From request to resultA complete plan you can follow.
Visible planThe problem
CRM exports can leak excessive customer data or create duplicate async jobs when scope, authority, polling, and retention are left implicit.
AI can validate and reconcile the export lifecycle while the provider action and StackOS artifact boundary own execution and data handling.
What the agent does
- Validate the bounded export plan and reject raw provider ids or unnecessary fields.
- Start the job once with a stable export key.
- Poll by safe job ref, consume the short-lived result internally, and reconcile artifact evidence.
When this workflow helps
A reusable method, adapted to the request.
- One bounded HubSpot contacts, companies, deals, leads, products, or line-items dataset must be exported for an approved purpose.
Before it starts
Connection required
- A HubSpot OAuth connection with the Bulk capability bundle
- A supported object type and provider-verified property refs
- Explicit export authority, a stable export key, and a retention policy
What proves it worked
Evidence, not a success claim.
- Reviewed export plan
- Safe async job and action-call refs
- StackOS artifact ref or truthful pending/repair guidance
Workflow path
The reusable stages of the work.
A real run expands these stages around the request, context, selected tools, approvals, and dependencies.
- 01Passes to next stage
Validate Export Intent
Read the bounded export request, prior export state, and recent action evidence before any provider call.
- 02Passes to next stage
Start Approved Export
Start exactly one provider export after explicit data-scope approval.
- 03Passes to next stage
Reconcile And Retrieve Export
Poll by safe job ref and, when complete, consume the provider result into the StackOS-managed artifact boundary.
- 04Verified outcome
Record Export Handoff
Store the durable export index and retention disposition for completed, pending, partial, blocked, or failed outcomes.
Safe stopping and recovery
Useful even when the whole path cannot run.
- Stop before provider creation when scope or export authority is incomplete.
- Stop with a safe pending handoff when the provider job is not complete.
- If provider state is pending, retain the safe job ref and next poll guidance without starting another export.
- If result download is partial or fails, reuse the same job and action evidence rather than creating a replacement job.
Specialists inside this workflow
Clear roles for each part of the job.
Connected work