Workflow Tool Stack

Connect the tools your task needs.

Bring the task and the tools your team uses. We check which connections are available and agree on access before connecting your accounts.

Map your workflow Book a mapping session
Tool fit

What each part of the system does.

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.

Substrate is our database and work view. It keeps records, tasks, approvals, and results together.

  • Operating state
  • Human review
  • Receipts
Agent environment
OpenAI provides the AI models and coding tools we use.

We use OpenAI with agreed permissions and tests. The same tool definitions and checks help us evaluate Claude, open-weight and custom models when needed.

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

Cloudflare provides hosting, storage, and background tasks. We document ownership and recovery for the services we use.

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

Build around the tools your team already uses.

Search the connector directory
Built on
OpenAI Cloudflare
Connects to
Google Workspace Slack Salesforce HubSpot Airtable Webflow

These logos identify available connections. They do not imply partnerships or endorsements. Account access and permission to change records are agreed 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 Available to connect. Account access still needs approval.

A listing means a connection is available. It does not mean an account is connected, an integration has been delivered, or a vendor has certified or endorsed us.

What you keep

See how the tools work together.

The plan shows each step, who approves it, when the system stops, and what record is kept.

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

Choose the task before choosing the tools.

Plan the task with the person responsible. Agree on what the system can do and when it must stop. If you deliver client work, read the service-provider guide.

Map your workflow Book a mapping session Use it with clients
Owner
Workflow owner
Authority
Named tool 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.