FlowRunner
PricingContact
Theme
Start Free

Connect AI agents to Teamwork.com. Agents spin up projects and task lists when a client is onboarded, turn tickets and form submissions into assigned tasks, log billable time entries, and keep tasks updated as work progresses.

12 actions Basic auth available
Teamwork website ↗ Platform Documentation ↗ Capability data verified 2026-07-28
A deal closes won in the CRM and client onboarding begins
Create Project sets up the engagement with the client company, start date, and end date
Create Task List builds the standard phase lists from the delivery playbook: kickoff, build, review, handoff
List People pulls the roster so the agent can propose assignees by role
The delivery lead reviews the proposed staffing, the one thing no playbook knows is who actually has capacity this week, and confirms or reassigns
Create Task writes the kickoff tasks with due dates, priorities, and the confirmed responsible parties
The project link and task summary post to the client channel, and the kickoff shows up on everyone's list before the first call

What This Integration Enables

Teamwork is built for client work, which means the data inside it is not just a to-do list, it is the basis of what clients get billed. That raises the stakes on automation in a specific way: creating projects and tasks by machine is pure leverage, while writing billable time by machine is a claim about money that a client will eventually audit. FlowRunner agents work the whole projects, task lists, tasks hierarchy, and treat the time-tracking boundary with the respect a client invoice deserves. - Spin up complete project structures, project, task lists, tasks, assignees, when a client is onboarded - Turn form submissions, tickets, and CRM records into assigned tasks with due dates - Keep external reports in sync by listing projects, tasks, and people on a schedule - Log time entries against tasks, with billable entries held for review - Mark tasks complete and update details as work moves through your delivery pipeline

Without FlowRunner

Onboarding is a half-day of clicking Every new client means recreating the same project, lists, and thirty tasks by hand, slightly differently each time
Requests die between systems Client asks arrive in forms, tickets, and email, and become tasks only if someone remembers to transcribe them
Time gets logged at month end Billable hours are reconstructed from memory during invoicing week, and the client bill inherits the guesswork

With FlowRunner

Projects assemble themselves Closed deals become fully structured projects in minutes, identical to the playbook every time
Every request becomes an assigned task Form submissions and tickets land in the right task list with a responsible party and a due date
Time flows in continuously and gets reviewed once Entries log against tasks as work happens, and the account lead approves the billable set before it touches an invoice

Use Case Scenarios

The client request that never gets lost

A client submits a change request through [Typeform](/integrations/typeform). The agent identifies the client's project with List Projects, finds the change-requests list via List Task Lists, resolves the account manager's ID from List People, and calls Create Task with the request text, a priority based on the client's tier, and a due date from the SLA. The client gets a confirmation, the account manager gets an assigned task, and the request exists in exactly one authoritative place.

The status report that compiles itself

Every Friday morning, List Projects pulls active engagements, and List Tasks walks each project's lists for what completed, what is overdue, and what is due next week. The agent writes the roll-up to [Google Sheets](/integrations/google-sheets) and posts a per-project digest to [Slack](/integrations/slack) with overdue items called out by name. The Monday status meeting starts with everyone looking at the same picture, and the project managers spent zero minutes producing it.

Time reconciled weekly, billed confidently

Timers run in [Harvest](/integrations/harvest) while the work happens. Weekly, the agent matches those entries to Teamwork tasks and drafts the corresponding Log Time entries, attributed to the right person, marked billable where the contract says so. The account lead reviews the billable set, strikes anything questionable, and approves. Entries post to the tasks, and invoicing week becomes an export instead of an archaeology dig.

Human-in-Loop Highlight

Log Time with the billable flag is the write in this connector that ends up on a client's invoice. Every automated billable entry is a statement to a paying client about what they owe, and a wrong one costs you twice: once in the awkward credit memo, and again in the client's new habit of scrutinizing every line you send. So FlowRunner workflows never let billable time flow straight from a timer to the record. The agent assembles the week's entries, matches them to tasks, attributes them to the right people with the date and description filled in, and stages the set. The account lead reads the list, hours, tasks, people, client, and approves it before Log Time writes anything flagged billable. Non-billable internal time can flow freely; the gate sits exactly on the line where hours become money. An agent can reconcile a timesheet perfectly. Standing behind the invoice is the account lead's job, and the workflow is built so they actually can.

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

12 actions

Projects

3
  • List Projects Lists accessible projects with status filters, active, current, late, upcoming, completed, plus name search and pagination. The lookup that starts nearly every flow on this page.
  • Get Project Retrieves one project's full details: name, description, status, company, dates, and category.
  • Create Project Creates a project with a name, optional description, company association, and start and end dates. The first move of every automated onboarding.

Task Lists

2
  • List Task Lists Lists the task lists inside a project. The targeting step that routes new tasks to the right group of work.
  • Create Task List Creates a task list within a project. Used to stamp out the playbook's phases identically on every engagement.

Tasks

5
  • List Tasks Lists a task list's tasks, complete and incomplete, with content, due date, priority, and assignees. The read behind status reports and overdue sweeps.
  • Get Task Retrieves one task's full details, including the responsible party. The context call before updates and escalations.
  • Create Task Creates a task with content, description, due date, priority, and a responsible person resolved via List People. The action that turns requests from other systems into owned work.
  • Update Task Changes only the fields you provide on a task, content, description, due date, priority, or assignee. The write for reprioritization and reassignment flows.
  • Complete Task Marks a task done without touching its other fields. The clean signal that lets downstream reporting and notifications fire on real progress.

People

1
  • List People Lists the account's people with names, emails, company, and admin status. Supplies the person IDs that assignment and time attribution depend on.

Time Tracking

1
  • Log Time Logs a time entry against a task with hours, minutes, date, and description, optionally attributed to a specific person and marked billable. The action this page's human gate exists for: billable entries wait for the account lead.

Frequently Asked Questions

What can FlowRunner do with Teamwork?

FlowRunner agents can run List Projects, Get Project, and Create Project in Teamwork, plus 9 more actions.

Does connecting Teamwork to FlowRunner require OAuth?

No. Teamwork connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can Teamwork trigger a FlowRunner workflow automatically?

Teamwork doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Teamwork

$100 in credits. No card required. Connect in minutes.