Actions

Everything a flow can do, including messages, lists, tags, properties, and webhooks.

Actions are the steps that actually do something. Drag them from the Actions section of the block palette, or insert them with the + buttons between nodes.

The flow editor with the block palette on the left

Send text message

Sends an SMS to the contact. Two modes:

Write message: compose the text inline, with the same personalization fields as blasts.
Use template: pick a saved SMS template. If you haven’t made any yet, the editor links you to create one.

Messages from flows respect the flow’s delivery window and land in the contact’s normal conversation thread, so replies show up in your inbox.

Sends a designed or plain-text email. Click Edit email to open the same composer used by email blasts: subject, preview text, and either the block builder or rich text. Requires email to be enabled on your workspace with a verified sending domain.

Add to list / Remove from list

Adds the contact to (or removes them from) a static list of your choice. Combined with the Added to list trigger, this is how flows chain together: flow A adds contacts to a list, which triggers flow B.

Add tags / Remove tags

Adds or removes tags on the contact record: type a tag and press Enter. Tags are searchable on the Contacts page and usable as segment criteria, so tagging inside flows (“attended-open-house”, “vip”) builds audiences for later.

Set property

Sets a custom property on the contact: a Property key and a Value (string, number, boolean, or date). Useful for stamping state like welcome_completed: true that other segments or flows can key off.

Create task

Creates a task for your team when the contact reaches this step, linked to the contact automatically. Set the title, description, and tags, optionally pick an assignee (who gets a push notification), and give it a relative due date, for example due 2 days after the step runs. Great for making sure automated outreach gets a human follow-up: send a message, wait, then create a “call if no reply” task.

Webhook

Sends an HTTP request to an external URL when the contact reaches this step. Click Edit webhook to set the URL and shape the payload; contact fields can be merged in. This is the escape hatch for anything Helios doesn’t do natively: notify Slack, write to a Google Sheet via Zapier, hit your own API.

Wait

Technically in the Time section of the palette, but you’ll use it constantly between actions: pause the flow for a period (or until a specific date) before continuing. Details in Logic and timing.

Per-step recipients

On an active flow, every action node links to a recipients view showing exactly who has hit that step, which is handy for debugging why someone did or didn’t get a message.