awork Make integrationAutomate awork with Make.
What could awork do on its own if your other tools could talk to it? The awork Make integration gives you 19 modules: 2 triggers and 17 actions on tasks, projects, companies and time entries. This guide connects your account and walks you through a first working scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What can the awork Make integration automate?
The awork Make integration links your awork workspace to Make, a no-code tool where you build a scenario: a chain of steps that runs by itself. Each step is a module. awork brings 19 of them, so new tasks and logged hours can flow into your other apps, and events elsewhere can create work inside awork.
Closed deal, project ready. When a deal is marked as won in your CRM, Create a Company and Create a Project set up the client and its project in awork, and Create a Task drops the kickoff to-dos into it. Nobody retypes the client name three times.
Hours that reach billing. Watch Time Entries picks up every new entry, Get a Project adds the project context (provided the entry carries its project ID, which your first Run once will show you), and the next module sends the line to your invoicing or accounting tool. Handy for any small agency that bills by the hour.
Tasks your team hears about. Watch Tasks spots each new task and a chat module posts it in the right channel, so account managers see new work without refreshing awork.
Some limits are worth knowing upfront. Both triggers are scheduled: Make checks awork on the scenario's schedule instead of being called the moment something changes. There is no search module either, so to act on an existing task you need its ID from a trigger or another module. When a listed module stops short, Make an API Call reaches the rest of the awork API with the same connection.
awork also has a node on n8n: see the awork n8n integration page, or the n8n vs Make comparison to pick your tool. New to Make? The Make training starts from zero.
How do you connect awork to Make?
- 01
Create a client application in awork
In awork, open Settings > Integrations and click Add new client application. Give it a unique name and a display name. If awork asks for a callback URI, paste
https://www.integromat.com/oauth/cb/awork. - 02
Copy the two credentials
Copy the Client ID shown in the list of client applications, then the Client secret displayed right after you create the application. Keep both at hand: Make asks for them in the next step.
- 03
Create the connection in Make
Add any awork module to your scenario and click Create a connection. A connection is your awork account linked to Make once, then reused by every awork module. Name it in Connection name if you like, paste the credentials or follow the on-screen instructions.
Your first scenario: a won deal becomes an awork project
GoalWhen a deal is won in your CRM, Make creates the matching project in awork and adds its first task.
- 01
Start a new scenario
From the Scenarios page, create a new scenario and click the big +. Pick the module of your CRM that watches for won deals: that is what starts everything.
- 02
Add Create a Project
Click the + on the right of the CRM module, search for awork and choose Create a Project. Click Create a connection and use the credentials from the steps above.
- 03
Map the deal into the project
Fill the project fields by mapping data from the CRM module, like the deal or client name. Once the connection works, Make lists what it can read in awork, so you pick instead of typing.
- 04
Chain Create a Task
Add Create a Task after the project module and, if the module offers a project to attach it to, pick the one Make just created, so the kickoff task lands in the right place instead of floating on its own.
- 05
Test with Run once
Click Run once, then mark a test deal as won. Open each module's bubble to read the bundle it received, the item passed along. Check awork: the project and its task should be there.
- 06
Schedule and switch on
On the first module, set the schedule (every 15 minutes by default) and turn the scenario on. Each module run counts as one operation on your Make plan.
What can start an awork scenario?
2 modules start a scenario when something happens in awork. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by awork as soon as it happens.
Watch Tasks
Scheduled triggerIn Make“Triggers when new task is created.”
Watch Tasks notices every task created in awork since its last check and hands each one to the rest of your scenario as its own bundle. It is the natural starting point when a new piece of work should ripple out to other tools.
Watch Time Entries
Scheduled triggerIn Make“Triggers when new time entry is created.”
Watch Time Entries collects the time entries logged in awork since the previous run, one bundle per entry. Hours tracked by the team can then travel to billing, payroll or a reporting sheet without anyone exporting a file.
What can the awork modules do?
awork gives you 17 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Create a Company
ActionIn Make“Creates a new company.”
Adds a client company to awork from data coming out of another app, so the account exists before any project is attached to it. The sales team keeps working in its CRM and awork stays in sync.
Create a Project
ActionIn Make“Creates a new project.”
Opens a fresh project in awork with the details mapped from earlier modules. For an agency, this is the module that turns a sale into planned work without a project manager copying anything by hand.
Create a Task
ActionIn Make“Creates a new task.”
Puts a new task into awork from any event your scenario catches: a support email, a form answer, a row added to a sheet. The request becomes something the team can plan instead of a message lost in an inbox.
Create a Time Entry
ActionIn Make“Creates a new time entry.”
Logs a time entry in awork on the team's behalf. Useful when hours are captured somewhere else, like a calendar or a timer app, and awork should still hold the full picture for budgets and billing.
Delete a Company
ActionIn Make“Deletes a chosen company.”
Removes a company from awork. It mostly serves cleanup scenarios, when a client record was created by mistake or a lead never became a real account and should disappear from the workspace.
Delete a Project
ActionIn Make“Deletes a chosen project.”
Erases a project from awork, given the project you point it to. It closes the loop on the Create a Project flow when a sale falls through before any work started.
Delete a Task
ActionIn Make“Deletes the specified tasks.”
Takes a task out of awork when it no longer makes sense, for example because the request behind it was withdrawn in another tool. It keeps boards honest without anyone hunting for stale cards.
Delete a Time Entry
ActionIn Make“Deletes a chosen time entry.”
Wipes a time entry from awork. Pair it with a validation step elsewhere, like a manager rejecting hours in a sheet, so the logged time and the approved time stay the same.
Get a Company
ActionIn Make“Returns an information about chosen company.”
Reads one company from awork and passes its details to the next modules. Handy when a trigger only gives you a reference and you need the client's full record to write an email or fill a document.
Get a Project
ActionIn Make“Returns an information about chosen project.”
Pulls the details of a single awork project into your scenario. Once you hold a project ID, this module fills in the context that a report or an invoice line needs.
Get a Task
ActionIn Make“Returns an information about chosen task.”
Fetches one task and its current details from awork. Triggers only see new tasks, so this is how a scenario looks at a task again later, once someone has worked on it.
Get a Time Entry
ActionIn Make“Returns an information about chosen time entry.”
Returns a single time entry with the information awork keeps on it. It lets a scenario double-check an entry before acting, instead of trusting a copy saved in another tool that may be out of date.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
Sends your own request to the awork API through the connection you already set up. It covers whatever the ready-made actions skip, for example finding items with no ID to start from, if the awork API supports it: check its reference.
Update a Company
ActionIn Make“Updates an information about chosen company.”
Changes the details of an existing company in awork with fresh data from another app. The CRM stays the place where sales edit client records, and awork follows without a second round of typing.
Update a Project
ActionIn Make“Updates an information about chosen project.”
Edits a project that already exists in awork. Status changes decided elsewhere, in a quote tool or a client approval flow, can then show up in the project without the project lead updating it by hand.
Update a Task
ActionIn Make“Updates a chosen task.”
Modifies an awork task when something changes in another tool. A reply from the client, a moved deadline in a calendar or a closed ticket can each nudge the task forward without a message to the team.
Update a Time Entry
ActionIn Make“Updates a chosen time entry.”
Corrects a time entry already saved in awork. It suits review flows where a manager adjusts hours in a spreadsheet or an approval app and the change should land back in awork automatically.
Need help automating awork with Make?
A person reads every message.
