Once your Autotask account has been connected, we can then set up the configuration to sync the Google and Microsoft contracts. 

Service Mapping

Before we can synchronize your contracts, we need to know which product matches which Autotask service. These services are then added to your Recurring Contracts in Autotask based on your selection. 


  1. Click on ‘Configure’ from the Configure page on the right-hand menu. 


  2. The products sold by your connected account are listed along with each possible billing cycle on the left side of the table. Map them to your Autotask services by using the drop-downs on the right. 

    Note: if you don't offer all services, that's no problem. Only map those services you need.

  3. Press the Save Mappings button to store your selection.




Advanced Configuration

  1. Complete the configuration steps that best suit your business use case and then click on ‘Save Configuration’. 

  • Never change the contract status - when it becomes suspended. Zomentum connect updates the status to Inactive by default. 

  • Days before renewal - This determines the number of days that Goolash will look ahead for expirations. If an Autotask contract's end date falls within this amount of days, it will be renewed by pushing its end date forward one year.

  • Name for New Contracts -  You can customize the format of the contract names for new contracts. The name of existing contracts will remain untouched. By default, we use the following format: %title% for %customer%

    For example, if you have a Google Workspace Basic subscription for the domain foobar.com, the contract title in Autotask will be - Google Workspace Basic for foobar.com.

    You can edit this field to match your current naming conventions. You can use the following dynamic variables:

  • %customer%: Customer name. This variable must always be present.

  • %title%: A descriptive title for the contract, generated by Goolash.

  • Default Contract Period - We try to determine the contract billing period based on the subscription information we receive from the vendor. If we are unable to determine this, as is the case with Microsoft CSP licenses, we will fall back to the globally configured period. By default, this is set to yearly.