lexisOS
Setting things up…
Setting things up…
A workflow step exists for LinkedIn, email, and SMS sends, alongside branching, delays, and CRM updates — around 30 step types in total, each one auto-send or approval-required, your choice.
linkedin.connect and linkedin.message can run through your stored session directly. Like, comment, post, visit profile, follow, unfollow, withdraw invite, and endorse skill route through your paired browser instead, by design. Connect and message default to holding for approval unless a step is set otherwise.
email.send checks your suppression list and builds the merge-field content before anything goes out. It defaults to sending automatically — set the step to approval-required and it inserts a Draft and notifies the approver instead.
sms.send is checked against consent before it dispatches — a contact who replied STOP is blocked outright, regardless of the step’s approval setting. Like email, it defaults to sending automatically.
Mark any LinkedIn, email, or SMS step “needs approval” and the run holds it as a Draft and waits until someone signs off — enforced by the workflow itself, not by a screen. Leave a step on its default and LinkedIn connect and message hold for approval, while email and SMS send automatically. Every default can be changed per step.
The content is generated and attached to the step.
Only if that step is set to approval-required — the run pauses here.
A person on your team signs off, or the step was set to send automatically.
The message goes out under your account’s caps and consent checks.
The rest of the ~30-step catalog a multichannel sequence draws from.
Kick off a workflow manually, on a schedule, when a signal fires — a role change, a company change, a keyword mention — from an inbound webhook, or on another product event.
branch.if and branch.email_event route the run differently depending on a field value, or on whether a prior email was opened, clicked, or replied to.
lead.update_status, add_tag, add_note, and assign — or the contact equivalents, including create_deal — run as steps in the same workflow, not a separate integration.
zoho.push and hubspot.push are workflow steps too, so a workflow can push a record to your CRM sync the moment it qualifies.
Start free and build a workflow that branches by channel — approval is a setting on the step, not a separate tool.