All customers of AutoTask PSA can use the Bedrock Autotask Connector.
You will need to generate a unique authentication token for installing the Connector. Follow steps below to generate this token.
- Go to https://www.base64encode.org/
- Input the user and pass joined by a colon, like: `username:password`
- Press “Encode”
- The resulting string (something like `dXNlcm5hbWU6cGFzc3dvcmQ=`) is your token
For the URL, follow the below table to determine what is the right URL to input for your instance of Autotask:
|America East 2||https://webservices14.autotask.net/atservices/1.5/atws.wsdl|
|America West 2||https://webservices15.autotask.net/atservices/1.5/atws.wsdl|
|London Data Center (Formerly Global 1)||https://webservices4.autotask.net/atservices/1.5/atws.wsdl|
|London Data Center 2||https://webservices16.autotask.net/atservices/1.5/atws.wsdl|
|Spain, Latin America||https://webservices12.autotask.net/atservices/1.5/atws.wsdl|
The resulting authentication in Bedrock will look something like this:
Each object below may have a certain set of sub-objects. Not all sub-objects are supported by Bedrock Data so it's important to discuss any specific data points related to these objects that are important to your integration needs with our sales team.
|Object||Permissions||Custom Field Support||Dedupe Key|
|Contact||Read / Update / Create||Yes|
|Account||Read / Update / Create||Yes||Name|
|Opportunity||Read / Update / Create||Yes||Expected Close Date Name Contact and Company Relationship|
API Version and Limits
We support the 1_5 version of the Autotask API. Learn more about this version via the following documentation provided by Autotask.
There is a 10,000 API call / Hour limit and this is for all integrations you may have associated with your account.
Every Connector has a set of requirements that can impact how data will flow from one system to another. These may not be the only limitations depending on your integration needs. Make sure to discuss your key integration goals with your Bedrock Data sales representative to ensure we can meet your needs.
Required Contact Fields
Account Name / ID
What you map to this field must have an exact match value for either the ID of your companies that exist in AutoTask or an exact match for the Company Name (i.e. Acme, Inc. won't match with Acme).
This will always default to a value of TRUE, which is represented as '1' in the default mapping column in Bedrock.
Required Company Fields
Since you need to ensure that a contact is added to an existing Company in Autotask, you must also map and sync your Company records from your marketing/sales system to Autotask to ensure that contacts will sync as expected. Here are the required fields for creating Accounts in Autotask.
Usually new companies created in Autotask by way of your sales/marketing system will default to something like 'Prospect' and these default values will be setup within your Bedrock Mapping. In the screenshot below the '3' represents the Prospect option in Autotask.
For this field, you can either opt to set a default owner value for each new company you created or you can setup a custom field in your marketing/sales system that stores all of the owners in a drop down making sure to either use their exact match name or ID as it is stored within Autotask. In the below screen shot we are just setting it each new company to a default owner where we are using their ID for the default value.