Workflow Tool Stack

Choose the right tool path for one controlled workflow.

Start with the workflow your team wants to delegate. CREATE SOMETHING maps the owned operating state in Substrate, then the agent environment, runtime, approval path, and evidence before any external tool gets more authority.

Map one workflow Talk through one workflow
Tool fit

CREATE SOMETHING owns the record. Each external platform gets one job.

CREATE SOMETHING owns the system. Cloudflare provides infrastructure. OpenAI provides intelligence. Substrate keeps workflow state, operator review, decisions, and evidence under CREATE SOMETHING control.

Owned substrate
Substrate keeps the operating record.

Use Substrate for source records, workflow state, human review, decisions, receipts, and the API/MCP boundary the system owns.

  • Operating state
  • Human review
  • Receipts
Agent environment
OpenAI is the primary reasoning and agent environment.

Use OpenAI for reasoning and agent-operable delivery, with scoped tools, approval behavior, and grounded evidence. MCP contracts, policy, and evals preserve the route to Claude, open-weight and custom models.

  • Reasoning layer
  • Agent delivery
  • Portable contracts
Runtime
Cloudflare runs the route.

Use Cloudflare when the workflow needs owned runtime behavior, durable state, and rollback paths.

  • Workers and Pages
  • Durable state
  • Rollback path
Tool compatibility

Built on a controlled core. Connected to the tools your team already uses.

Search every connector →
Built on
OpenAI Cloudflare
Connects to
Google Workspace Slack Salesforce HubSpot Airtable Webflow

Brand marks identify tool paths, not partnerships or endorsements. Accounts, permissions, and write access are scoped for each workflow.

Connector directory

Search the available tool paths.

984 brokered connector paths are listed. Availability is a starting point; connection, permissions, actions, and approval rules are verified during workflow mapping.

984 results Connector available ≠ connected or write-authorized

Directory entries indicate a brokered connector path, not a live customer connection, delivered integration, certification, partnership, or endorsement.

What you keep

The useful output is a map, not a vendor diagram.

The first artifact should tell an operator what happens, who owns the decision, where the system stops, and what proof remains.

Map
Workflow map

The handoff, owner, source systems, allowed actions, and risk boundary.

Boundary
Tool boundary

Which tool reads, writes, routes, waits, stops, or asks for approval.

Control
Approval path

What can run automatically, what needs a person, and what must stop.

Proof
Evidence trail

Runbook, receipt, rollback note, or review surface the operator can keep.

Map the workflow

Bring the workflow before choosing the stack.

I’ll map the handoff, owner, connected systems, allowed actions, approval pauses, stop points, and evidence path before implementation starts.

Map one workflow Talk through one workflow
Owner
Partner operator
Authority
Named delivery boundary
Proof
Shared workflow receipt
State
review
  1. 01 / Agent environment OpenAI

    Primary reasoning and agent delivery.

  2. 02 / Runtime Cloudflare

    Owned route and state.