In order to perform a successful connection to your Teamwork instance, we just need the following information and that's it!
- Teamwork Domain: The full domain of your Teamwork account, e.g. https://mydomain.teamwork.com (Tip: be sure to exclude the "/" on the end.)
- API Key: Your Teamwork API key. You can find this by clicking your avatar when logged into Teamwork > API.
Once we have a successful connection, it will enable us to populate your AlertFind instance with the following information :
- First Name
- Last Name
- User Name
- Email/Alternate Emails
- Work Phone (Ext.)
- Fax number
- Zip Code
How does our Teamwork connector works :
The graphic below explains the various nodes involved in the transition of data from your Teamwork instance to AlertFind.
Detailed Steps Explaining Above Graphic :
- Teamwork connector fetches the User Information stored in your instance via API.
- Based on your chosen frequency, our connector running on AWS Lambda fetches data from Teamwork instance.
- At this stage, data goes through validation and processing and is transformed into a CSV.
- The CSV is compressed into a Zip file and sent to AlertFind API via the AlertFind connector running on AWS lambda.
Data Storage Nodes in Above Graphic :
- Node 5 : Refers to Apache Cassandra Cluster which stores the data for execution purposes. It has a TTL of 7 days after workflow execution has finished.
- Node 6 : Refers to Elastic Search Cluster used for indexing data for 30 days so that it can be searched within the log’s interface.
- Data Safety: All Data is encrypted in transit via HTTPS, using TLS 1.3 encryption internally. Sensitive customer data, such as access tokens, usernames and passwords are encrypted at rest using Amazon Key Management Service (KMS), which uses FIPS 140-2 validated hardware security modules.
We encourage you to keep searching the connector that suits your needs in our main AlertFind Connector List under the section System of Records Integrations by clicking the button below.