Skip to main content
The Teamwork.com integration makes client delivery data available in your work. Ask how an engagement is tracking against its budget, which tasks are overdue before a milestone, or how many billable hours the team logged last week, and Hebno answers from Teamwork.com with each project, task and time entry cited. When a request implies a change, such as logging time or creating a task, Hebno shows a confirmation card and writes to Teamwork.com only after you confirm.

At a glance

Before you start

You need:
  • A Teamwork.com user on your site, for example yourfirm.teamwork.com or yourfirm.eu.teamwork.com.
  • An allowed integration. An owner or admin sets Teamwork.com to Allow under Admin → Connectors → Catalogue.
  • Time tracking turned on for a project to read or log time on it, and project permissions that let you log time.
  • Permission to view project budgets in Teamwork.com if you want budget figures in answers. A site administrator sets this in each project’s People settings.
Teamwork.com OAuth does not use scopes. Authorising Hebno issues a token for your user on your site, and Hebno then works with your own Teamwork.com permissions in each project. Hebno uses these parts of the Teamwork.com API:

Connect Teamwork.com

1

Start the connection

Open Settings → Connections, find Teamwork.com and select Connect. You can also select Connect from the prompt in a chat.
2

Sign in to Teamwork.com

Sign in, choose your site if you belong to more than one, and select Allow.
3

Return to Hebno

The card shows Connected with your site address.
Hebno reads and writes with your own permissions, so you see only the projects you are a member of in Teamwork.com, and budgets and time only where your project permissions allow them. Tokens are encrypted at rest. Select Disconnect at any time, or ask an admin to revoke the connection under Admin → Connectors → Connections.

What Hebno reads

Reads are live. Hebno queries Teamwork.com when a request needs it. Only what a reply used is stored with the conversation as its sources.
Excerpts a reply uses become part of the conversation. Anyone you share the conversation with can read them, including budget figures, task descriptions and comments from Teamwork.com.

What Hebno writes

Every write appears first as a confirmation card. You can change any field before you select Confirm.
Confirmation card for Teamwork.com with editable fields

A Teamwork.com change pending confirmation. Nothing is written until you confirm.

Hebno never deletes tasks, task lists or projects, changes budgets or rates, marks time as invoiced, creates invoices, or changes project permissions or site settings. Writes are made as your Teamwork.com user, so Teamwork.com shows you as the author. Linking marks which Teamwork.com projects belong to an engagement, so you can ask “how much budget is left?” without naming the project.
  1. Open the project and select Brain.
  2. Under Linked records, select Link record, then Teamwork.com.
  3. Search by project name or client company and select the project. Repeat for each Teamwork.com project in the engagement.
In chats tagged to the project, Hebno starts with the linked projects for any delivery or budget question, and cards for new tasks and time logs default to them. See Linked records.

Use Teamwork.com in chat

  • Attach: open the + menu, choose Sources → Teamwork.com, and pick a project, a task list, a task or a milestone. Or type / and choose Teamwork.com.
  • Ask: name the client, project, milestone or person in your request. For example:
    How is the Contoso pricing review tracking against its budget, and what is left before the readout milestone?
    List billable and non-billable hours on Contoso in October, by person and task list.
    Create a task in the Readout list to draft the steering committee deck, assign Sarah Chen, due 13 November, estimate 6 hours.
  • Research runs show a Checking Teamwork.com step, with a chip for each project, task and budget it read.
  • Agents can read Teamwork.com on a schedule, for example a Monday brief on budget used across active client projects. Writes an agent proposes appear in agent approvals for review.

Troubleshooting