Automation

Let the busywork run itself.

Build workflows on a visual canvas — when a lead comes in, a deal is won or an invoice goes overdue, OfficOne sends the email, creates the task, assigns the owner or calls your system.

Start free Book a demo

Part of the Business plan· from ₹7,999 a monthSee plans

Triggers across every module — schedules come on top: 21; Triggers across every module — schedules come on top
Actions, plus wait, if/else and end steps: 14; Actions, plus wait, if/else and end steps
Ready-made templates to start from: 7; Ready-made templates to start from
Delivery attempts for every webhook: 7; Delivery attempts for every webhook

What's inside

Automation you can read, test and trust.

Workflows are built on a canvas anyone on the team can follow — and every run leaves a record of exactly what it did.

Visual workflow builder
Triggers, if/else branches and waits on a canvas anyone can read. Test on a real record before switching it on.
Triggers across modules
New lead, deal moved or won, ticket created, message received, form submitted, invoice issued, paid or overdue, payment received, custom events from your app — or a schedule.
Actions
Send an email or WhatsApp, notify a teammate, create a task or deal, assign round-robin, update fields, tag, open a ticket, add to a sequence, post to Slack or call a webhook.
Waits that survive anything
"Wait 2 days, then check" — runs are stored safely and carry on even after a restart.
Run history
Every run, step by step, with what happened and why — so nothing automated is a mystery.
Signed webhooks
Send any event to your own URL, signed so you can verify it, retried with back-off and logged.
API & keys
Scoped API keys to read and write records, plus endpoints to send events and leads from your product.

Triggers & actions

Everything that can start a workflow — and everything it can do.

This is the actual list from the workflow builder. Each trigger brings its record's fields with it, so conditions and messages can use them.

Triggers

21 triggers + schedules

Sales

Lead or contact createdContact changedDeal createdDeal moved stageDeal wonDeal lostTask completedMeeting booked

Marketing

Lead capturedForm submitted

Inbox

Message received

Support

Ticket createdTicket status changedCustomer replied on a ticket

Billing

Quotation acceptedInvoice issuedInvoice paid in fullInvoice became overduePayment received

Accounting

Bill recorded

Your app & time

Custom event (API)On a schedule — daily, weekly or monthly

Steps

14 actions + 3 flow steps

Messages

Send an emailSend WhatsApp or SMS

Team

Notify a teammateCreate a task

Records

Assign an ownerUpdate a fieldAdd tagsRemove tagsCreate a dealOpen a ticket

Marketing

Add to an email sequenceRemove from sequences

Apps

Send to a URL (webhook)Post to Slack

Flow

WaitIf / elseEnd the workflow

Conditions, waits & re-entry

Precise about who it runs for, and how often.

Narrow a trigger with conditions on any of its fields, branch with if/else, and pause with waits measured in minutes, hours or days. Decide whether a workflow can run for the same record once, every time, or again after a cooldown. Then try it on a real record before you switch it on.

Operators: is, is not, contains, doesn't contain, more than, less than, is set, is empty, has tag, doesn't have tag
Match all conditions or any of them
Waits in minutes, hours or days that carry on after a restart
Run once, always, or again after a cooldown of 1 to 365 days
Check the conditions against a real record, or run a draft on one record

Run history

Nothing automated is a mystery.

Every run is listed with its record and status. Open one to see each step — what it checked, what it sent, which branch it took. Retry a run that failed, or cancel one that's waiting.

A list of runs per workflow, with status
Step-by-step detail for each run
Retry and cancel from the same screen
Runs waiting on a timer pick up again after a restart

For developers

Webhooks you can trust, and an API for your own product.

Send OfficOne events to your systems, and send your product's events and leads into OfficOne.

Signed webhooks

Every delivery carries a timestamped HMAC-SHA256 signature of the body. Failed deliveries are retried with back-off and logged; you can resend, send a test, and rotate the secret.

POST https://your-app.in/hooks/officone
x-officone-signature: t=1760421000,v1=9c1f…e04a

// verify: HMAC_SHA256(secret, t + "." + rawBody) === v1

REST API & keys

API keys scoped to the permissions you pick, with an optional expiry from 1 to 730 days.

Send us your events

POST /api/v1/events   600/min
POST /api/v1/leads    300/min

A signed_up or trial_ended from your app can start a workflow.

How a run works

From an event to a finished run.

1
Something happens
A deal is won, a form is submitted, an invoice goes overdue — or the schedule comes round.
2
The conditions are checked
Against the record's fields. If they don't match, nothing runs.
3
The steps run in order
Messages, tasks, field updates, tags, webhooks — and if/else branches choose the path.
4
Waits are stored safely
A “wait 2 days” is saved with the run and continues on time, even after a restart.
5
The run is logged
Every step and its result goes into the run history for anyone to check.

Put it on autopilot

Start from a template.

These come ready in the workflow builder. Each one is editable and stays switched off until you turn it on.

When
Lead captured
IfIt's a new person
1. 1Email them a thank-you
2. 2Wait 2 days
3. 3If their lead status is still New, create a call task for the owner
When
Lead or contact created
IfLifecycle is Lead and there's no owner
1. 1Assign an owner round-robin
2. 2Notify the new owner
When
Deal won
1. 1Update the person's lifecycle to Customer
2. 2Create a kick-off meeting task in 2 days
When
Ticket created
IfPriority is Urgent
1. 1Notify the chosen teammates
2. 2Post it to Slack
When
On a schedule: every Monday, 9:30 am
IfOpen deals with high priority
1. 1Notify each owner to check in
When
Custom event (API): signed_up
1. 1Add the tag “trial”
2. 2Add them to the onboarding sequence

Workflows are part of the Business plan. Each one starts switched off, and you can test it on a real record first.

Questions

Automation, plainly answered.

Something else? Ask us in a demo.

Which plan includes Automation?

The Business plan, along with Accounting.

Will a new workflow start sending emails straight away?

No. Workflows start switched off. Check the conditions against a real record, or run the draft on a single record, and switch it on when you're happy.

What happens if OfficOne restarts while a workflow is waiting?

Nothing is lost. Waits are stored with the run, and runs that were mid-step pick up again after a restart.

Can I connect Slack?

Yes — paste a Slack incoming-webhook URL and the “Post to Slack” step can send messages to that channel.

Can my own product trigger workflows?

Yes. Send a custom event to the events API — for example signed_up — and any workflow using “Custom event (API)” with that name will run. You can also create leads through the leads API.

How do I verify a webhook really came from OfficOne?

Each request has an x-officone-signature header with a timestamp and an HMAC-SHA256 of the timestamp and body, using your endpoint's secret. Compute the same and compare.

One workspace

Works together with

Every module shares the same people, team and history — nothing to sync, nothing to re-type.