Workflow automation

Workflow automation services that pass work between your apps without retyping

We connect the apps you already use, so a form, a deal stage or a payment starts the next job and odd cases reach a named person.

Tell us which handoff to build first
Trusted by the world's fastest-growing brands

What a workflow is

One trigger, a few steps, and the apps they touch

Workflow automation services build the chain that runs when something happens in one of your apps: a form is submitted, a deal changes stage, a payment clears. Each link in the chain is a step in another app, and the build is the wiring between them.

Work order WO-1187DispatchedSample Gulfview Property ManagementTampa, FLStarted by the portal form, 9:12 a.m.Unit214TriggerCategoryPlumbingSort stepPhotoAttachedTriggerVendorVendor B, acceptedOffer stepTenantVisit window by textConfirm step

The trigger

The event that starts a run: a new row, a new email in a shared inbox, a changed field in the CRM. We pick the trigger that fires once per real event, so a lead enters the chain a single time and a duplicate does not start a second run.

The steps

What happens next, in order: look up a record, check a field, create a task, send a message. Each step names the app it acts in and the data it needs from the step before. A step that cannot find its data stops and says which field is missing.

The handoff

The last link puts the work in front of a person or another system with the details attached: a work order with the unit and photo, a deal with the source and the first reply. The person receives the finished handoff with the details attached.

Who builds it

Built and documented for you, or built in-house on a platform

Both routes land in the same tools. They differ in who builds the first workflow, who writes down how it works, and what happens when an app changes underneath it.

Built in-house on a platformYour team buildsBuilt for you, one workflow at a timeWe build, you approve
Who buildsA team member learns the tool and builds between other tasksA strategist scopes it, and the build follows your written approval
Where it livesThe accounts of whoever set it up, unless moved laterAccounts in your name from the first day, with us invited as users
Odd casesAdded as they turn up in live runsWritten as rules before the build, each routed to a named person
DocumentationWhatever the builder chose to write downA step map, a field list and a run log are part of the scope
Cost shapeStaff time plus the platform planA price per workflow, set against the hours it returns
Which should you pick?

Build it in-house when the chain is two apps and one rule, and someone on your team enjoys the tool. Hand it over when a run crosses three or more apps, touches money or customer messages, or has to keep working after the person who built it moves on.

What the sources say

What Zapier, n8n, Make and the FTC publish, and what we do with it

Four come from tool documentation and two from the FTC. The source and the date we read it sit under each one, and they set how we size a plan, handle failures and send messages.

  1. Plan sizeWhat counts as a task

    In Classic Zaps, Zapier says trigger steps never use tasks, and neither does any Filter or Paths step.

    The same page lists steps from Formatter and Delay as not using tasks either, and says each completed run of a Next Gen Zap uses at least one task. A workflow’s plan size therefore follows its action steps, so we count the action steps in one run and multiply by the runs you expect before suggesting a plan.

  2. BurstsConcurrency

    In self-hosted n8n, concurrency control is disabled by default, and it applies only to production executions started by a webhook or trigger.

    When a limit is set, runs over it are queued and processed first in, first out. For a workflow that receives a burst, such as form entries after a mailing goes out, we set a limit so the extra runs wait their turn in order.

  3. RetriesIncomplete runs

    Make’s Retry error handler stores incomplete executions and enables automatic or manual retries.

    Its Skip handler disregards the error and moves to the next bundle. We choose Retry for a step that calls an outside app that can time out, and Skip only where a missed record would not matter to anyone.

  4. Half-finished runsCommit or rollback

    Make’s Commit handler stops a scenario and saves the processed changes, while Rollback stops it and reverts the changes of modules that support transactions.

    A workflow that writes to two systems can fail between the writes, and Make cannot undo actions made by modules without transaction support. We decide per workflow whether a stopped run keeps what it finished or undoes it where the app supports it, then test the choice on a sample record before any real one is touched.

  5. Opt-outs10 business days

    The FTC’s CAN-SPAM guide says a business must honor a recipient’s opt-out request within 10 business days.

    A follow-up workflow that emails leads has to know who opted out. We build a suppression list that the workflow reads before it sends, and a step that adds an address to the list the moment someone unsubscribes. Your counsel sets the legal reading.

  6. ResponsibilitySending on your behalf

    The FTC’s guide says a business cannot contract away its legal responsibility by hiring another company to handle its email.

    A workflow tool sends under your name, so the duties stay with you. That is why the scope lists each message the workflow can send, with its trigger and its unsubscribe handling, and why you approve that list before anything goes live.

The scope

What workflow automation services produce

Six parts of one working workflow. Each part is set up in your accounts and comes with a short document describing it.

Step map · dispatch5 stepsTriggerSortCreateOfferConfirmOffer to the approved vendorStep 4 of 5AppText messagingActionTexts the category’s vendorHand off ifNo vendor accepts in 2 hours

The trigger and step map

We draw the chain from the event that starts it to the last action: a request form, a status change, a payment. Each step names its app and what it passes on. You receive: a step map with the trigger, each step, its app and the cases that go to a person.

Connections4 connectedTenant portalWebhookSends new requestsWork ordersReady connectorRead and createText messagingAPISends texts onlyShared emailReady connectorSends email onlyEvery login is a Gulfview account

App connections

We connect the apps the chain touches, through a ready connector where one exists and through a webhook or the app’s API where it does not. Sign-ins use accounts you own. You receive: a connection list showing each app, the access level it was given and who owns the login.

Field map2 filtersPortal formWork order listUnit numberUnitRequest textCategorySortPhotoPhotoContinue only if the unit number is presentand the estimate is not over $500.

Field mapping and filters

We match each field in one app to its place in the next, and add filters so a run only continues when the data qualifies: a unit number is present, an amount is under a limit. You receive: a field map, plus the filter conditions written in plain sentences.

Maintenance desk1 new caseWorkflow11:13 a.m.No vendor accepted within 2 hours.Unit308 · HVACOffered toVendor D, 9:13 a.m.Sent toMaintenance coordinatorTake the caseOpen request

Exception routing

Cases that break a rule leave the chain and go to a named person with the details attached, in a place your team already looks. We write the rule and the name together. You receive: an exception list showing each rule and who receives the case.

Error plan1 alertStepRetrySkipStopSort requestCreate work orderOffer to vendorConfirm to tenantRun stopped at Create work orderRequest 1192 · office manager told

Error handling and alerts

We choose, step by step, whether a failure retries, skips or stops the run, and who is told. A failed run raises an alert with the step name and the record it stopped on. You receive: an error plan listing the handling for each step and the alert recipients.

Run historySample monthReceived150No edits120To a person30Emergency wording12No vendor accepted in 2 hours9Missing unit or photo6Estimate over $5003

Run history and handover

The workflow records each run and its outcome in a table your team can read without opening the tool. We walk you through changing a rule or a recipient yourself. You receive: the run history, a one-page guide to editing the workflow and the logins transferred to your named owner.

How it runs

From a trigger to a workflow you can read

You approve the scope, then each stage in turn, and each stage leaves you a document for your files. The samples follow a fictional property manager, Sample Gulfview Property Management in Tampa, FL.

step-map.csv

Step map: maintenance request

Sample · Sample Gulfview Property Management, Tampa, FL
StepWhat it doesGoes to a person when
Trigger: portal formA submitted request starts the runThe unit number or photo is missing
Sort by categoryLabels the request plumbing, electrical, HVAC or appliance, and flags emergency wording such as flooding or no heatEmergency wording is found: the on-call manager is texted at once
Create the work orderAdds unit, category, photo and tenant contact to the work order listThe estimated cost is over $500
Offer to the approved vendorTexts the vendor listed for that category and waits for a replyNo vendor accepts within 2 hours
Confirm to the tenantSends the visit window by text if the tenant agreed to texts, otherwise by emailThe tenant replies that the problem has changed
A step goes live once you have seen it pass on test records. The texts the workflow can send are listed in the scope, with the opt-out handling for each.

Our stack

The tools the workflows run on

Each one can start a run, move data or send a message. We choose by the job and the volume, and the account is yours.

Zapier
Why Zapier

A hosted tool that chains a trigger to actions across a very large catalog of apps, set up through forms rather than code.

How we use it

We build in it when the chain is short and linear, such as a new form entry creating a CRM contact and a task. Billing runs from your own subscription.

IntegrationsSpeedNo-code
ZapierYes
MakeYes
NativeSome
ManualNo

Questions

Workflow automation services, answered

Start here

Get a written scope for the first workflow

Tell us which handoff you retype most. You get the steps, the apps, the task count and the price in writing, and you decide after reading it.