Connecting apps and adding App Action steps

Workflows aren't limited to what SAMI OS does on its own. You can push and pull data to outside tools — your CRM, scheduler, e-signature app, and more — by connecting an account and dropping an App Action step (or starting from an App Trigger) right inside the builder.

Browse the app catalog

Open a workflow from Workflows and add a step (or open the trigger picker). The app picker shows a curated catalog grouped into categories so you can find the right tool fast:

• Core Platform — SAMI OS itself, the native CRM, communication, and AI actions.
• CRM & Sales Intelligence — CINC, Follow Up Boss, GoHighLevel, HubSpot, and Apollo.
• Artificial Intelligence (AI) — OpenAI, ElevenLabs, and Veo.
• Productivity & Collaboration — Slack, Notion, Microsoft Teams, and Monday.
• Scheduling & Meetings — Calendly and Cal.
• Documents & E-Signatures — BoldSign and Signaturely.

Data Enrichment, Marketing & Design, and Operations categories round out the list. Each app card shows how many actions and triggers it offers.

Connect an account and add an App Action

You connect the app right where you build the step — no trip to Settings required.

1. Pick the app and action

   Add a step, choose an app from the catalog, then select the action you want — for example Create Person in Follow Up Boss or Create Contact in GoHighLevel. The step panel opens on the right with the app and action shown at the top. Use Change to swap either one.

2. Log in to the app

   Under Account, click Log in to [app]. You're sent to the provider's secure login, then returned to the same workflow with the account connected. If you already have one connected account, SAMI OS selects it for you.

3. Choose the connected account

   The action runs as the account you pick here, so the right records get created or updated. If you've connected more than one account for an app, select the correct one from the Account list.

4. Map data into the fields

   Once an account is chosen, the Fields to fill section unlocks. Type fixed values, or use the data picker to insert values from the trigger or an earlier step — like {{contact.email}} or {{contact.firstName}}. Fields marked Required must be filled; Required when used fields only matter when you supply them.

5. Test the step

   Use Test Step to send a dry run and confirm the action behaves before you rely on it. The result appears inline so you can copy any output values into later steps.

Start a workflow from an App Trigger

Some apps can also kick off a workflow. Open the trigger picker, choose an app, and pick a trigger — for example New Person in Follow Up Boss or New Lead for Contacts coming from CINC. In the trigger's Required setup, connect and select the account SAMI OS should listen to, the same way you do for an action. Then build the rest of the sequence with native steps or more App Actions.

For lead sources that send data over a webhook instead of a login, see the lead-received webhook trigger guide. To review every native step alongside these App Actions, open the Workflows builder palette.

Related articles

• Capturing leads with the Lead Received webhook trigger
• Automating CINC leads with workflows
• Workflow steps: every action you can add