awork

awork is project management for agencies and teams, built around projects, tasks and time tracking with a light CRM attached. Agents open projects from templates, create and complete tasks, book time, and start flows in real time when work is created, moved or finished.

1 trigger 53 actions API key available

awork website Platform Documentation Capability data verified 2026-08-18

A project's status moves to Completed in awork

List Project Time Entries pulls every hour booked against it, with its billable and billed flags

Agent checks that each billable entry is also marked billed against an invoice that actually went out

Agent isolates the hours that were never invoiced and the tasks still open on a completed project

Agent posts the unbilled hours and the open tasks to the delivery lead with the totals attached

Set Time Entries Billed marks the entries the lead confirmed as already invoiced

The lead decides what happens to the project itself, because deleting it takes the tracked time with it

What This Integration Enables

awork is project management for agencies and internal teams, built around projects, tasks and time tracking with a light client record attached. One design decision shapes every flow you build on it: an awork API key is admin level and workspace wide, and its webhooks are too. The key does not act as a person, it acts as the workspace, and the trigger sees every matching change regardless of who made it or which team it belongs to. That is a real capability, because an agent gets a view no individual account holds. It is also the reason the discipline has to live in the flow.

FlowRunner agents use that reach the way a good operations lead would. They open projects from templates when a deal closes, book time against the right task from wherever the work was recorded, mark entries billable and billed as invoices go out, push approved leave into the capacity view, and answer what changed on a project this week from the trigger's own change list. The writes that decide what work is worth, and the ones that destroy the record of it, are where FlowRunner's human-in-the-loop step belongs. Every action is built and verified against the awork API.

Without FlowRunner

Closeout depends on memory A project is finished when someone says so, and the unbilled hours on it are found later or not at all

Client updates written twice The task moves to Done in awork, then someone retypes the same fact into an email

Capacity planning misses approved leave Absences live where they were approved, so the workload view shows people who are not there

With FlowRunner

Closeout is a checked list Every completed project reports its unbilled hours and its still-open tasks before anyone calls it done

Status moves become client updates A task reaching Done produces the update it implies, in the channel the client reads

Leave reaches the capacity view Approved time off is written into awork so planning sees the same people the calendar does

Use Case Scenarios

A won deal becomes a project that is already set up

A deal closes in HubSpot. The agent looks for the client with List Companies and calls Create Company when it is genuinely new, then calls Create Project with a project template id so the engagement arrives with its task lists and tasks already in place rather than as an empty shell. List Project Types tells it which workflow the project should follow, because the type carries the status set the project can move through. Set Task Assignees puts named owners on the tasks the template left open, and a summary posts to Slack. What used to be twenty minutes of setup on a Monday is a side effect of the deal closing.
Status changes that turn into the client update they imply

The workspace-wide trigger fires when a task moves into a done status. The agent reads the change list on the delivery, pulls the task with Get Task, and decides whether this is a milestone the client cares about or internal housekeeping. When it matters, it drafts the update from the task's own name, dates and tracked duration, and routes it for a quick read before it goes. Because the trigger is workspace wide, this works across every project without one flow per team, and because it ignores user permissions, the flow rather than the token decides which projects are in scope.
Weekly reconciliation of tracked time against what was billed

On a schedule, the agent calls List Time Entries with a filter for the period, groups them by project, and compares each project's hours against the plan. Entries marked billable but not billed are the ones that represent money not yet asked for, and they go to the delivery lead as a list. When an invoice is issued in Xero or QuickBooks Online, the agent runs Set Time Entries Billed on exactly the entries that invoice covered, so the two systems tell the same story. Approved leave from the people system lands as Create Absence, which removes that capacity from the workload view where the planning is actually done.

Human-in-Loop Highlight

awork ships no archive for a project. Change Project Status can move a finished engagement out of the way, but the only operation that removes one is Delete Project, and it permanently deletes the project together with its tasks, its lists and its tracked time. The same trap sits one level down: Delete Tasks will optionally take the tracked time with the tasks, which is why it defaults to keeping it. Deleting the time destroys the record an already-issued invoice was built from. So the closeout agent never deletes. It posts: "Harbour Redesign has been Completed for 60 days. It holds 412 tracked hours, 38 of them billable and not yet marked billed, and 4 tasks still open. Deleting the project removes all 412 hours from every total that included them, and awork offers no archive. Delete, or move it to the Closed status and leave the record standing?" The lead answers. In practice the answer is usually the status change, which is the point: the agent surfaced a decision that would otherwise have been made by whoever was tidying up that afternoon.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

53 actions

Account

Get Current User Retrieves the user and workspace the API key belongs to. Because an awork key grants admin level access rather than acting as one person, this is how a flow confirms which workspace a connection reaches.

Projects

List Projects Retrieves a page of projects. Search matches a project name for the common case, and a full filter expression covers anything more specific.
Get Project Retrieves one project by its id, including its status, members, task counters and tracked duration.
Create Project Creates a project. Supplying a project template id copies that template's task lists and tasks, which is how a repeatable engagement is opened in one call.
Update Project Replaces a project's editable fields. awork requires the name on every update, so flows pass it through even when it is unchanged.
Change Project Status Moves a project into a different status. Statuses are defined per workspace, so a flow reads them rather than assuming an id.
Change Project Type Moves a project onto a different project type. The type carries the workflow and the status set, so this can also change which statuses the project may be in.
Delete Project Permanently deletes a project with its tasks, lists and tracked time. There is no project archive in awork, which is why the human gate on this page sits here.
List Project Members Retrieves the members of a project, with the role each holds and who is responsible.
Remove Project Member Removes a member from a project. Time they already tracked against it is kept.
List Project Statuses Retrieves the project statuses defined in the workspace, which are the values a status change expects.
List Project Types Retrieves the project types defined in the workspace. A type carries the workflow a project follows, so it is worth choosing deliberately at creation.

Tasks

List Project Tasks Retrieves a page of tasks in one project. awork publishes no list-all-tasks route, so tasks are read within a project or through the personal list.
List My Tasks Retrieves the project tasks the connected identity can see, across every project. Because the key is admin level, this is a workspace wide view.
Get Task Retrieves one task by its id, including its status, assignees and planned duration.
Create Task Creates a task. The base type decides whether it belongs to a project or is private to one person, and planned duration is given in minutes.
Update Task Replaces a task's editable fields. awork requires the name on every update, so flows pass it through even when it is unchanged.
Delete Tasks Permanently deletes one or more tasks, optionally taking their tracked time with them. Deleting the time destroys billing history, which is why it defaults to keeping it.
Set Task Assignees Assigns a list of users to a task, replacing whoever was assigned before. An empty list clears the assignment entirely.
Set Task Priority Raises or clears the priority flag on a task, which is what pins it to the top of a person's list.
Change Task Statuses Moves one or more tasks into a task status. This is how progress is recorded, and it accepts a batch so a whole column moves at once.
List Task Statuses Retrieves the task statuses of a project, which are the columns of its board and the values a status change expects.

Task Lists

List Task Lists Retrieves the task lists of a project. Lists group tasks inside a project, separately from their status.
Create Task List Creates a task list inside a project.
Add Tasks To List Adds tasks to a task list. A task can sit in more than one list, so this adds rather than moves.
Remove Tasks From List Removes tasks from a task list. The tasks survive; only the list membership is dropped.

Time Tracking

List Time Entries Retrieves a page of time entries across the workspace, filtered by user, project or date range. The read a billing reconciliation starts from.
List Project Time Entries Retrieves the time booked against one project, which is what a project profitability check reads.
Get Time Entry Retrieves one time entry by its id, including its billable and billed flags.
Create Time Entry Books time for a user. awork requires the user, the type of work and a timezone on every entry, because it stores local and universal times side by side.
Update Time Entry Replaces a time entry's fields, with the same three required values as creation.
Delete Time Entry Permanently deletes a time entry. The hours come off every total that included them, including any billing figure already reported.
Set Time Entries Billable Marks time entries billable or unbillable in a batch. This decides what can be invoiced, so it changes what the work is worth.
Set Time Entries Billed Marks time entries as billed or unbilled in a batch. Billed records that the time has actually been invoiced, which is distinct from whether it is billable at all.
List Type Of Work Retrieves the types of work defined in the workspace. Every time entry needs one, and it is what decides how the time is rated.

Users

List Users Retrieves a page of workspace users. Archived users are excluded unless a flow asks for them.
Get User Retrieves one user by their id.
Set User Active Activates or deactivates a user. Deactivating frees the seat and blocks sign in without deleting anything the person did.
Set User Archived Archives or unarchives a user. An archived user disappears from pickers but keeps their history.

Companies

List Companies Retrieves a page of companies, the client records projects are attached to.
Get Company Retrieves one company by its id.
Create Company Creates a company. Only the name is required, so a client captured from a form can be created immediately and enriched later.
Update Company Replaces a company's fields, with the name required on every update.
Delete Company Deletes a company. awork refuses while projects still reference the record.

Teams

List Teams Retrieves the teams in the workspace. A team groups users and projects together.
Create Team Creates a team in the workspace.
Set Team Users Adds users to a team or removes them. Team membership decides who sees the team's projects.

Absences

List Absences Retrieves a page of absences, the holidays and other non working periods capacity planning takes account of.
Create Absence Records an absence for a user, which removes their capacity from the workload view for those dates.
Delete Absence Deletes an absence, returning the user's capacity for those dates.

Webhooks

List Webhooks Retrieves the webhooks configured in the workspace, including the ones FlowRunner created for its triggers.
List Webhook Logs Retrieves the delivery log of one webhook, with the response code and failure reason per attempt. This is how a trigger that never fired is told apart from one whose endpoint was rejecting deliveries.
List Webhook Event Types Retrieves the event types a webhook can subscribe to, straight from awork, so a flow confirms the vocabulary rather than assuming it.

Triggers

1 triggers

Event Triggers

On Workspace Event Fires when the selected event happens anywhere in the awork workspace. awork webhooks are workspace wide, so this sees every matching change regardless of who made it or which team it belongs to, and user permissions are not applied. Choosing any event delivers all of awork's event types through a single trigger, which is what makes a one-flow-for-the-whole-workspace pattern practical rather than requiring one subscription per team.

Frequently Asked Questions

What can FlowRunner do with awork?

FlowRunner agents can run Get Current User, List Projects, and Get Project in awork, plus 50 more actions.

Does connecting awork to FlowRunner require OAuth?

No. awork connects to FlowRunner with an API key, no OAuth flow required.

Can awork trigger a FlowRunner workflow automatically?

Yes. awork supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with awork

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us