Workflow blueprints
Blueprints for moving work between two systems without losing the accountability.
Each blueprint covers one source-to-destination pairing: what the source emits worth acting on, what the destination can safely accept, and the failure mode that specific pairing produces.
Pair-specific
Written for the two systems, not generically
Failure-first
The exception path designed alongside the happy path
One owner
Each field written by exactly one side
Introduction
Why these are organised by pairing.
The hard parts of a handoff are properties of the two systems involved. Chat to CRM has a signal-selection problem; ledger to payments has an idempotency problem; repository to tracker has a loop problem. Generic integration advice covers none of them.
Each blueprint therefore states what that pairing specifically gets wrong, and what the design has to do about it. That is more useful than a list of steps that would apply to any two systems.
They assume you keep both systems. The pattern is to preserve whatever is authoritative and connect through a governed workflow rather than consolidating.
- Unit
- One source → destination pair
- Assumes
- Both systems stay
- Covers
- Happy path and exception path
- Deeper detail
- Integration guides
Why this exists
Handoffs fail in ways specific to the systems on each end.
Integrations are usually designed around the happy path, and the happy path is the part that was never going to be difficult. What determines whether the workflow survives is what happens when a record is ambiguous, a provider is down, or an event is delivered twice.
Those failure modes are not generic. Deciding which chat messages are events at all is a different problem from deciding whether a retried payment write will duplicate a record, and a design that treats them the same will get one of them wrong.
The other recurring failure is bidirectional writes without a single owner per field, which produces update loops that are obvious in hindsight and invisible in design review.
You're likely here because
- A handoff works in testing and degrades in production
- Duplicate records appear after an integration goes live
- Two systems keep overwriting each other
How to choose
Finding the right blueprint.
If
You know both systems
Start with
Find the matching pairing in the list below
If
You know one system and want implementation depth
If
You are not sure which systems should be involved
Start with
Describe the outcome to ARIA firstIf
You need the decisions written down before building
Start with
The workflow discovery templateHow it works
The five stages every blueprint follows.
The systems change; this sequence is what makes a handoff debuggable.
Step 01
Detect
Subscribe to the specific event that should start work rather than everything the source emits.
Step 02
Resolve identity
Match the event to the existing destination record before anything is created; route ambiguous matches to review.
Step 03
Assemble context
Attach the surrounding history and ownership so the decision uses full context rather than one event.
Step 04
Gate and act
Apply the policy and approval boundary, then write only the fields the workflow is permitted to own.
Step 05
Measure and correct
Track completion and exceptions, and raise failures visibly rather than dropping them.
Blueprints
Documented pairings — 20 in total.
Slack → Salesforce
Slack to Salesforce: workflow automation guide
A practical guide to connecting Slack and Salesforce around moving qualified team signals into CRM follow-up, including workflow design, implementation, controls, measurement, and the UbiGrowth path for extending the automation into a broader operating workflow.
Read the workflow →Gmail → HubSpot
Gmail to HubSpot: workflow automation guide
A practical guide to connecting Gmail and HubSpot around connecting reply context to CRM records and next actions, including workflow design, implementation, controls, measurement, and the UbiGrowth path for extending the automation into a broader operating workflow.
Read the workflow →Google Drive → Salesforce
Google Drive to Salesforce: workflow automation guide
A practical guide to connecting Google Drive and Salesforce around turning documents and structured files into usable account context, including workflow design, implementation, controls, measurement, and the UbiGrowth path for extending the automation into a broader operating workflow.
Read the workflow →Shopify → HubSpot
Shopify to HubSpot: workflow automation guide
A practical guide to connecting Shopify and HubSpot around connecting customer and order signals to lifecycle marketing and sales, including workflow design, implementation, controls, measurement, and the UbiGrowth path for extending the automation into a broader operating workflow.
Read the workflow →QuickBooks → Stripe
QuickBooks to Stripe: workflow automation guide
A practical guide to connecting QuickBooks and Stripe around reconciling billing and payment context across finance systems, including workflow design, implementation, controls, measurement, and the UbiGrowth path for extending the automation into a broader operating workflow.
Read the workflow →GitHub → Jira
GitHub to Jira: workflow automation guide
A practical guide to connecting GitHub and Jira around keeping engineering delivery and work tracking aligned, including workflow design, implementation, controls, measurement, and the UbiGrowth path for extending the automation into a broader operating workflow.
Read the workflow →Calendly → HubSpot
Calendly to HubSpot: workflow automation guide
A practical guide to connecting Calendly and HubSpot around turning booked meetings into attributable CRM activity, including workflow design, implementation, controls, measurement, and the UbiGrowth path for extending the automation into a broader operating workflow.
Read the workflow →Slack → Google Calendar
Slack to Google Calendar: workflow automation guide
A practical guide to connecting Slack and Google Calendar around coordinating team requests with scheduled work, including workflow design, implementation, controls, measurement, and the UbiGrowth path for extending the automation into a broader operating workflow.
Read the workflow →Meta Ads → Salesforce
Meta Ads to Salesforce: workflow automation guide
A practical guide to connecting Meta Ads and Salesforce around connecting campaign response to pipeline outcomes, including workflow design, implementation, controls, measurement, and the UbiGrowth path for extending the automation into a broader operating workflow.
Read the workflow →LinkedIn → HubSpot
LinkedIn to HubSpot: workflow automation guide
A practical guide to connecting LinkedIn and HubSpot around moving social prospecting context into a governed revenue workflow, including workflow design, implementation, controls, measurement, and the UbiGrowth path for extending the automation into a broader operating workflow.
Read the workflow →Stripe → QuickBooks
Stripe to QuickBooks: workflow automation guide
A practical guide to connecting Stripe and QuickBooks around reconciling payment events with accounting workflows, including workflow design, implementation, controls, measurement, and the UbiGrowth path for extending the automation into a broader operating workflow.
Read the workflow →Notion → Slack
Notion to Slack: workflow automation guide
A practical guide to connecting Notion and Slack around surfacing knowledge changes where teams communicate, including workflow design, implementation, controls, measurement, and the UbiGrowth path for extending the automation into a broader operating workflow.
Read the workflow →Asana → Google Drive
Asana to Google Drive: workflow automation guide
A practical guide to connecting Asana and Google Drive around connecting project execution to files and deliverables, including workflow design, implementation, controls, measurement, and the UbiGrowth path for extending the automation into a broader operating workflow.
Read the workflow →ClickUp → Slack
ClickUp to Slack: workflow automation guide
A practical guide to connecting ClickUp and Slack around surfacing project events without manual status chasing, including workflow design, implementation, controls, measurement, and the UbiGrowth path for extending the automation into a broader operating workflow.
Read the workflow →AWS → Datadog
AWS to Datadog: workflow automation guide
A practical guide to connecting AWS and Datadog around connecting infrastructure events to operational observability, including workflow design, implementation, controls, measurement, and the UbiGrowth path for extending the automation into a broader operating workflow.
Read the workflow →Cloudflare → Datadog
Cloudflare to Datadog: workflow automation guide
A practical guide to connecting Cloudflare and Datadog around combining edge and application signals for incident response, including workflow design, implementation, controls, measurement, and the UbiGrowth path for extending the automation into a broader operating workflow.
Read the workflow →Supabase → Slack
Supabase to Slack: workflow automation guide
A practical guide to connecting Supabase and Slack around routing application events into bounded team workflows, including workflow design, implementation, controls, measurement, and the UbiGrowth path for extending the automation into a broader operating workflow.
Read the workflow →Google Analytics → HubSpot
Google Analytics to HubSpot: workflow automation guide
A practical guide to connecting Google Analytics and HubSpot around connecting acquisition behavior to CRM lifecycle context, including workflow design, implementation, controls, measurement, and the UbiGrowth path for extending the automation into a broader operating workflow.
Read the workflow →Microsoft Teams → Salesforce
Microsoft Teams to Salesforce: workflow automation guide
A practical guide to connecting Microsoft Teams and Salesforce around moving account collaboration signals into revenue execution, including workflow design, implementation, controls, measurement, and the UbiGrowth path for extending the automation into a broader operating workflow.
Read the workflow →Gmail → Google Calendar
Gmail to Google Calendar: workflow automation guide
A practical guide to connecting Gmail and Google Calendar around turning email intent into scheduled follow-up without losing context, including workflow design, implementation, controls, measurement, and the UbiGrowth path for extending the automation into a broader operating workflow.
Read the workflow →Scope
What a blueprint does not cover.
- It does not replace provider documentation for API specifics.
- It assumes both systems remain authoritative for their own records.
- Rate limits, bulk paths, and event guarantees are set by the providers.
- Consequential actions stay behind human approval, which bounds how much of a pairing can run unattended.
FAQ
Questions about this collection.
My pairing is not listed. Does the pattern still apply?
Usually. The stages are the same; what changes is the specific failure mode of the two systems. The nearest listed pairing by system type is normally a good starting point.
How is this different from an integration guide?
A blueprint covers moving work between two named systems. An integration guide covers one system in depth — its object model, auth, and constraints. Most implementations use both.
Do these require replacing either system?
No. The whole pattern assumes you keep both and connect them through a governed workflow.
Can a blueprint run bidirectionally?
Only with an explicit owner per field and echo-event filtering. Bidirectional writes without those are the most reliable way to produce an update loop.
How much runs without a person?
Routine bounded handoffs, once proven. Consequential decisions stay under human authority regardless of measured reliability.
Where should the first one start?
The handoff performed most often with the clearest ownership. Prove it end to end, including the failure path, before adding a second.
Start with ARIA
Ask ARIA about workflows.
You do not have to pick your way through this collection to get started. Describe the outcome you want and ARIA determines which capabilities, systems, and workflows the job needs.
- ARIA acts only through the systems and permissions you connect.
- You can change or revoke any connection at any time.
- Every action is recorded, and anything significant can require your approval first.
Start here
Prove one handoff before you build the second.
Describe the handoff that costs the most time today. ARIA resolves which systems participate, what has to be true for the write to be safe, and where the human boundary belongs.