Configure Teamwork.com as a Source in your Pipeline

Perform the following steps to configure your Teamwork.com Source:

1. Click Pipelines in the Navigation Bar.

2. Click + Create Pipeline in the Pipelines List View.

3. On the Select Source Type page, select Teamwork.

4. On the Select Destination Type page, select the type of Destination you want to use.

5. In the Configure Source screen, specify the following:

   

   • Source Name: A unique name for your Source, not exceeding 255 characters. For example, Teamwork Source.

   • In the Connect to Teamwork section, specify the following:

     • Username: The API token that you copied from your Teamwork.com site.

     • Password: Any value, such as X. Teamwork.com ignores the password when you authenticate with an API token.

     • Teamwork Site URL: The address of your Teamwork.com site, as shown in your browser. For example, https://yoursite.teamwork.com. Specify only the site address, not the link to a page in the site. For a site in the EU region, the address is of the form https://yoursite.eu.teamwork.com.

6. Click Test & Continue to test the connection to your Teamwork.com Source. Once the test is successful, you can proceed to set up your Destination.

Data Replication

Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline.

For the Activity, Calendar Event, Comment, Project, Project Budget, Task, Users, and Workflow objects, Hevo ingests new and updated records in each Pipeline run, as per the sync frequency. Changes are identified using the time at which a record was last updated. In the first run, Hevo ingests all the records updated since January 1, 2008.

For all the other objects, Hevo ingests the entire data during each Pipeline run.

You can resync only the parent objects. When you resync a parent object, Hevo also resyncs its child objects.

Teamwork.com limits the number of API requests that can be made per minute, based on your plan. If this limit is exceeded, a rate limit exception occurs. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.

Note: You can create a Pipeline with this Source only using the Merge load mode. The Append mode is not supported for this Source.

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.

Click to view ERD

The primary key of most objects is id. The following objects use other primary keys:

• Users: user_id.

• The child objects that link two records, such as Project User, Task Tag, and Workflow Project, use the IDs of both records, for example, project_id and user_id.

• Company Tag, Milestone Tag, Milestone Tasklist, Project Budget Notification, Team Member, and Tasklist Tag: id and the ID of the parent record, for example, company_id.

• Milestone Change Follower, Milestone Comment Follower, and Milestone Responsible Party: milestone_id and the ID of the person, such as change_follower.

• Task Change Follower, Task Comment Follower, and Task Complete Follower: task_id and the ID of the person, such as change_follower.

• Task CRM Deal: task_id and crm_deal.

• Task Workflow Stage: task_id and index.

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline: