Draw a workflow once. When something happens in your sheets, on a schedule, or in a connected app, Atwork takes it from there.
A workflow begins the moment something happens — in your data, on the clock, or out in the world.
A row is created, a field is updated, a deal moves stage — react to any change in any sheet, down to the exact column.
Every morning, every Monday, the first of the month — timezone-aware schedules with full cron-level control when you want it.
Put a button on your rows. Whoever clicks it starts the workflow for exactly that item — approvals, publishing, escalations.
A Form Studio submission lands as a row and can immediately kick off routing, replies and follow-ups.
Connect your inbox over IMAP. New mail becomes a trigger — turn requests into tracked work automatically.
Connected apps bring their own triggers — a Telegram message, an email in your inbox. When it happens in a tool you've connected, it can start a workflow.
Pick a team — every one of them automates a different corner of the same workspace.
A deal moves to Won. The workflow creates the onboarding task with a due date, assigns the account owner, and posts the summary to the sales channel on Telegram — the customer never waits on an internal memo.
Every morning the workflow sweeps the pipeline for deals with no activity in 14 days and nudges the owner — silence never becomes a lost quarter.
A deal moves to Won. The workflow creates the onboarding task with a due date, assigns the account owner, and posts the summary to the sales channel on Telegram — the customer never waits on an internal memo.
Deal moved to Won → Create onboarding task → Post to sales channel
Every morning the workflow sweeps the pipeline for deals with no activity in 14 days and nudges the owner — silence never becomes a lost quarter.
Every morning → Idle for 14+ days → Nudge the deal owner
An editor presses the Publish button on the content row. The workflow posts the piece to LinkedIn, flips the status to Published, and leaves the post link on the row — one click, full trail.
Publish button pressed → Post to LinkedIn → Mark as Published
A newsletter signup lands as a row, joins the subscribers sheet, and the welcome email goes out from your own address — while the interest is still warm.
Newsletter signup → Add to subscribers → Send welcome email
A support email arrives in the connected inbox. If it's from a VIP account, the workflow assigns the on-call teammate and pings the support channel — the customer gets an answer while others are still triaging.
Support email arrives → From a VIP account → Assign on-call teammate → Alert support channel
Every hour the workflow checks for tickets unanswered past four hours and escalates them to the team lead's channel — SLAs hold without anyone watching a clock.
Every hour → Unanswered for 4+ hours → Escalate to team lead
Every Monday at 8:00, collect last week's numbers across sheets and email the digest to the team — timezone-aware, and nobody has to remember.
Every Monday, 8:00 → Build weekly digest → Email it to the team
Thirty days before a contract renewal, the workflow creates the renewal checklist and puts it in the account manager's hands — with a month to act, not a weekend.
Renewal in 30 days → Create renewal checklist → Assign account manager
A candidate submits the application form. The workflow adds them to the candidates sheet and creates the intro-call event on Google Calendar — recruiting keeps moving overnight.
Application submitted → Add to candidates → Schedule intro call
An offer is marked Accepted. The workflow creates the onboarding checklist and emails the welcome pack — the new hire's first day starts prepared, not improvised.
Offer marked Accepted → Create onboarding checklist → Send welcome pack
A bug is marked Critical. The workflow pulls its due date to today and alerts the release channel — no critical issue sits unseen in a backlog.
Bug marked Critical → Set due date to today → Alert release channel
A feedback form submission is checked for the bug tag; real bugs become tracked rows in the bug sheet automatically — nothing valuable dies in a spreadsheet export.
Feedback submitted → Tagged as a bug → Create bug row
Between a trigger and its actions, conditions decide what continues. Combine field comparisons, option checks and date windows — so the workflow acts exactly when it should, and stays quiet the rest of the time.
Triggers and actions plug straight into the tools around your work — Telegram, Slack, email, calendars, meeting links, and thousands more apps through Zapier and Make.