TASKS & WORKFLOWS

Automate the repetitive.

Onboarding sequences, post-payment kickoffs, contract-signed handoffs, the workflows you've been running by memory, written down once and triggered automatically by real events.

01 / Build once, run forever

Workflows you can trust.

Define a workflow's trigger and its actions, save it, and from then on every matching event runs the workflow. Onboarding becomes click-and-done. Contract handoffs become automatic. Your memory stops being the bottleneck.

02 / Triggered by real events

Five events, no scheduling.

Workflows fire when a contract is signed, an invoice is paid, a form is submitted, a task is completed, or a client signs in for the first time. There's no time-based scheduling, workflows respond to things that actually happen, which is usually what you want anyway.

03 / Tasks clients see

Work that lands in their portal.

Some workflow actions create work for your clients, a form to fill, a contract to sign. They see these in their portal next to everything else you've shared, not in a follow-up email you have to remember to send.

◆ EVERYTHING YOU GET

The whole toolkit, not just the headlines.

5 trigger types
Real events, not time-based
6 action types
Tasks, messages, forms, contracts, embeds, files
Client-assignable tasks
Visible deadlines in their portal
Milestones
Group tasks by phase
Board templates
Reuse project structure
Run history
Audit every fire, debug failures
◆ FAQS

Honest answers to common questions.

What events can trigger a workflow?+

Five today: a task is completed, a form is submitted, a contract is signed, an invoice is paid, or a client signs in for the first time.

Can workflows run on a schedule?+

Not today, workflows are event-driven. "Every Monday" isn't a trigger you can pick. For cadence-based behavior, look at your built-in notifications (overdue invoices, etc.) which run automatically.

What can a workflow do once it fires?+

Six actions: create a task, send a chat message, assign a form, assign a contract, assign an embed, or upload files into a folder. Actions can use placeholders pulled from the trigger event.

Where do I see what ran?+

Each workflow has a Run history tab showing every time it fired, what it did, and whether each action succeeded. Failed runs include the specific error.

Try the rest in your free workspace.

Book a demo and we'll walk you through setup, branding, and your first client portal — usually in under an hour.

Your brand. Their experience. One portal.

Join 50+ agencies who've already made the switch.

Reach out to our sales team

Tell us about your team, we'll come back with whether Almox fits and which tier makes sense.