Resources · Zapier integration

awork Zapier integrationAutomate awork with Zapier.

The awork Zapier integration gives you 5 triggers, 4 actions and 6 searches. All five triggers are instant: a new project, task or time entry in awork sets your automation off at once, free plan included. Here is what each one does, what it costs and where it breaks.

See the 15 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the awork Zapier integration actually does

awork handles projects, tasks and time tracking for businesses that sell their work by the project, all in one workspace. Plugging it into Zapier means awork can react to your other tools, and your other tools can react to awork, without anyone copying data by hand.

Three results people usually build first. A project that sets itself up: when New Project fires, Create Project Task drops the kickoff task into it, so nobody forgets step one. A client record that exists before the first call: a signed deal in your sales tool feeds Create Client, then Create Project. Hours that travel on their own: New Time Entry and Updated Time Entry push logged time toward your invoicing sheet the moment someone records it.

What it does not do matters just as much. There is no action to update or delete a task, a project or a time entry, and no trigger for a new client. Searches look things up by ID, by name or by email, nothing broader. Past that, the API Request (Beta) action is the escape hatch, and it is built for people at ease with an API.

Weighing platforms before you commit? The awork Make integration and the awork n8n integration cover the same app on the other two tools.

Vocabulary

Zapier words in one minute

Eight terms come back on every line of this page. Read them once and the rest goes faster.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts a Zap. Once the Zap is switched on, Zapier simply waits for it to happen.
Action
What the Zap does after it starts: the step that creates, sends or moves something for you inside an app.
Task
The unit Zapier bills. One action that completes successfully is one task, and your plan is a monthly count of those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment the event happens.
Filter
A step that lets the Zap continue only when what arrived matches the condition you set, and stops it there otherwise.
Search step
A step that finds something already sitting in an app, so the steps after it can reuse what it found.
Multi-step Zap
Anything beyond one trigger and one action. A second action, a filter or a search makes one, and it needs a paid plan.
Cost

What an awork Zap really costs

awork is not a premium app, so it works on the free plan. The trigger never costs a task. Each action that succeeds costs one, counted separately, and an action that fails costs nothing.

  • Free plan100 tasks a month, unlimited Zaps, two steps per Zap
  • TriggerNever billed
  • Each successful action1 task, counted on its own
  • awork triggers5 instant, 0 polling

The catch: the free plan stops at two steps. Put a filter or a search in front of Create Project Task and you need a paid plan. And since every awork trigger is instant, the interval grid below never slows these Zaps down. That grid only matters for polling triggers, and awork has none. Where the bill grows is the action side: a Zap that creates a client, then a project, then a task uses three tasks per run, not one. Count actions, not Zaps, when you size your plan.

Connect

Connect awork to Zapier in three steps

  1. 01

    Open your Zapier connections

    In Zapier, go to the Apps page and click + Add connection. You need an awork account first, plus read or write access to anything you do not own but want the Zap to touch.

  2. 02

    Find awork and start the link

    Type awork in the search box of the dialog, pick it from the list, then click Add connection. A new browser tab opens on the awork side, where the rest of the setup happens.

  3. 03

    Sign in and grant access

    Log in to awork in that tab and allow Zapier to reach your account. The connection is saved once, and every awork step you build later reuses it without asking again.

First Zap

Your first awork Zap: a kickoff task in every new project

GoalEach new awork project gets its kickoff task automatically, but only when a client is attached.

  1. 01

    Create the Zap

    Start a new Zap in Zapier, pick awork as the app that starts it, and choose New Project as the event. Select the awork connection you just made.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent projects of your account, so you map the next steps on a real project instead of a blank example.

  3. 03

    Add the filter

    Add a Filter step from the plus icon. Set the field to look at, the rule, and the value to compare with. This step makes it a multi-step Zap, so it needs a paid plan.

  4. 04

    Add the action

    Add awork again and pick Create Project Task. Map the project from the trigger, then fill in the task name, the type of work and the task status.

  5. 05

    Test, then publish

    Test the action once and check the task in awork. Then click Publish: each new client project now gets its kickoff task the moment it is created.

Triggers

awork triggers on Zapier

5 events start a Zap when something happens in awork, and 5 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Project

Instant trigger

In Zapier“Triggers when a new project is created.”

Starts the Zap whenever someone creates a project in awork, which makes it the natural entry point for anything that should happen at kickoff: a welcome message, a shared folder, a first task.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your agency opens a project for every signed client and wants the same setup to happen without anyone running through a checklist.
Watch out
it reacts to creation only, so a project that gets edited later will not set it off a second time.
2

New Task

Instant trigger

In Zapier“Triggers when a new task is created. The trigger only fires for tasks with a project assigned, not for private tasks.”

Reacts each time a task is added inside an awork project and passes it to the next step, so a fresh to-do can show up wherever your team actually looks during the day.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a creative lead wants every new task in a client project posted to the team chat without copying it over.
Watch out
private tasks never set it off. Only tasks that belong to a project count, so a personal to-do stays invisible to Zapier.
3

New Time Entry

Instant trigger

In Zapier“Triggers when a new time entry is created.”

Fires as soon as a person logs time in awork. That fresh entry becomes data the Zap can carry over to the billing or reporting tool the rest of the company relies on.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a studio bills by the hour and wants each logged block copied into the spreadsheet finance already works from.
Watch out
every entry runs the Zap once, and each action after it costs a task, so a team that logs often drains a free plan fast.
4

Updated Task

Instant trigger

In Zapier“Triggers when a task is updated. The trigger only fires for tasks with a project assigned, not for private tasks.”

Fires when an existing project task is updated in awork, so the steps after it can act on the task as it now stands.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a project manager wants the client told when a task reaches its final status, without typing the email each time.
Watch out
the trigger does not say which change it reacted to, so if only one status matters, add a filter on that status. Like New Task, it ignores private tasks.
5

Updated Time Entry

Instant trigger

In Zapier“Triggers when a time entry is updated.”

Runs when a time entry that already exists is corrected in awork. It closes the gap that New Time Entry leaves open: hours fixed after the fact.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your invoicing sheet must match awork even when someone rounds up yesterday's hours this morning.
Watch out
if the step after it only adds rows, a corrected entry shows up as a second line next to the first one.
Actions

awork actions on Zapier

awork gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Client

Action

In Zapier“Creates a new client.”

Adds a client to awork from data arriving in another tool. Only the name is required, so it works even when the source holds very little.

When to use it
a deal marked as won in your CRM should exist as a client in awork before anyone opens a project for it.
2

Create Project

Action

In Zapier“Creates a new project.”

Opens a new project in awork with a name and a project status, both required. Everything else can be filled in later by the team.

When to use it
a signed quote or a submitted brief form should turn into a ready project, so the kickoff meeting starts with something on screen.
Watch out
the status must already exist in your awork account, or there is nothing to pick.
3

Create Project Task

Action

In Zapier“Creates a new project task.”

Drops a task into a chosen awork project. Four fields are mandatory: name, project, type of work and task status. A priority flag is optional.

When to use it
a support request or a form reply should land as a task in the right client project instead of sitting in someone's inbox.
Watch out
map the project from an earlier step or a search, otherwise every task lands in the same one.
4

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

Sends a raw request to awork using the connection you already set up, for anything the ready-made actions do not cover. You choose the method and the address yourself.

When to use it
you need an awork operation that has no action here, and someone on the team reads API documentation comfortably.
Watch out
it only accepts addresses on awork's own domains, and the stop-on-error setting decides whether a failure halts the Zap.
Searches

awork searches on Zapier

6 search steps look for data that already exists in awork, so a later step can use it.

A search step looks up something that already exists in awork and hands it to the next steps. In the editor, awork searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not the one you expected.

1

Get Client by ID

Search

In Zapier“Finds a client by id”

Fetches one client when you already hold its awork ID, typically because an earlier step or another tool stored it.

When to use it
a project event gives you the client ID and the next step needs the full client record.
2

Get Project by ID

Search

In Zapier“Finds a project by id”

Pulls the full details of a single project from its awork ID. Handy when a trigger only passes the identifier and the action after it wants more.

When to use it
a time entry points to a project and your report needs that project's name next to the hours.
3

Get Task by ID

Search

In Zapier“Finds a task by id”

Retrieves one task by its awork ID. Useful when an outside tool kept the ID and you want the current state of the task, not the one stored back then.

When to use it
a ticket in your help desk references an awork task and the Zap must check where it stands today.
4

Search Clients

Search

In Zapier“Finds a client by name”

Looks up a client by name, which is how most other tools know a customer. The client found can then feed a project or a task created right after.

When to use it
a form gives you a company name and the new project must be attached to the matching awork client.
Watch out
whether the name must match exactly is decided by awork, so test with real spellings.
5

Search Projects

Search

In Zapier“Finds a project by name”

Finds a project by its name. This is the step that sends an incoming request to the right place before Create Project Task runs.

When to use it
emails tagged with a project name should become tasks in that exact project.
Watch out
if several projects match the name, the multiple-results setting above decides which one goes on.
6

Search Users by Email

Search

In Zapier“Finds a user by email”

Matches an email address with a person in your awork workspace. Email is the one detail most tools share, which makes this lookup the bridge between them.

When to use it
a request comes in from a teammate's address and the Zap needs that person as an awork user for the next step.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the dependent steps are skipped. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into find-or-create. No awork search offers it, so a missing client or project has to be created by a separate action.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When your awork Zap breaks

Zapier attaches no help article to awork and lists no limit specific to it. What breaks here are the general rules every Zap lives by.

  • Old projects never show up

    A Zap only reacts to what happens after you publish it. Projects, tasks and time entries created before that are never picked up, so moving the backlog is a separate job.

  • A Zap that sets itself off

    Start a Zap on New Task and make it create a task in awork: the task it creates starts the Zap again, and so on. That loop burns through your task count in no time.

  • A bulk import gets held back

    When a trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can pause it before it runs everything.

  • Private tasks stay silent

    New Task and Updated Task only fire for tasks inside a project. A teammate's private to-do will never start your Zap, however you set it up.
Need help

Need help automating awork with Zapier?

A person reads every message.

FAQ

awork Zapier integration: your questions

01Is the awork Zapier integration free?
Yes, as long as your Zap stays at two steps. awork is not a premium app, so it runs on Zapier's free plan, which gives you 100 tasks a month and as many Zaps as you like. The limit people hit is the shape of the Zap: one trigger and one action, nothing more. Add a filter, a search or a second action and Zapier asks for a paid plan. A simple New Project to Create Project Task Zap fits the free plan perfectly.
02How many tasks does an awork Zap use?
One task per action that succeeds, every time the Zap runs. The trigger itself is free, and so is a failed action. So a Zap with one action uses one task per new project, task or time entry, while a Zap with three actions uses three. Time tracking is where this adds up: if New Time Entry starts the Zap, each logged block of time runs it once. Count how often your team logs hours before choosing a plan.
03Does awork trigger Zaps in real time?
Yes. All five awork triggers are instant: awork tells Zapier the moment a project, a task or a time entry is created or changed, and the Zap starts straight away. The polling interval of your plan, 15 minutes on the free plan, does not apply to them. In the editor, these Zaps show a lightning bolt. That makes awork one of the easier apps to run well on a free account.
04What does it take to connect awork to Zapier?
An awork account and a Zapier account. You open the Apps page in Zapier, click + Add connection, pick awork, sign in on the tab that opens and grant access. If the Zap must touch projects you do not own, your awork user needs read or write access to them. For actions, prepare your awork account too: project statuses, task statuses and types of work must exist before Create Project or Create Project Task can use them.
05Why doesn't New Task fire for some tasks?
Because those tasks are private. New Task and Updated Task only fire for tasks that belong to a project in awork. A personal to-do with no project attached never reaches Zapier, whatever you change in the Zap. The fix happens in awork, not in Zapier: put the task in a project, or create it from a project directly. Once it sits in a project, every new task and every change to it starts the Zap as expected.
06What if the awork action you need is not listed?
Then the API Request (Beta) action is the way forward. It sends a request to awork with the connection you already set up, so you can reach operations the ready-made actions skip. It does expect someone comfortable with an API, and it only accepts addresses on awork's own domains. Test it on a single item before you switch the Zap on. If nobody on the team fits that description, it is worth checking whether Make or n8n covers the operation natively.
07Zapier, Make or n8n for awork?
Start from the operations, not the brand. On Zapier, awork exposes 15: five triggers, all instant, four actions and six searches, with nothing to update or delete outside API Request (Beta). If what you need sits in that list, Zapier does the job. If it does not, compare what Make and n8n expose for awork before you write raw API calls, and weigh the tool your team already runs and maintains.
Same platform

Other docs you might need on this stack.

Browse all integrations