Setting up Zapier and One Click Contractor

Step-by-step on how to connect One Click Contractor to Zapier

Note: In order to proceed with this documentation it does require you to have an account on zapier.com. You can do this by simply browsing to https://www.zapier.com and signing up for an account. 

Step 1: Connecting your Zapier Account with One Click Contractor

 

Note: The screens you will see may be slightly different as Zapier makes updates as well as the name and version number may change as we release updates to the integration. In the case of this documentation you’ll notice it says “Staging”.

 

Our Zapier integration is currently available “by Invitation Only”

To access, please follow the link to accept the invitation and Build your first Zap

https://zapier.com/developer/public-invite/121515/087d965cecd16431759e9652d6588754/

Click “Accept Invite & Build a Zap”

 

Step 2a: Make a Zap (One Click Contractor as Trigger)

From the left-hand or right-hand side of the window, click “Create”

 

 

The first step is configuring the “Trigger”. In this case, One Click Contractor is going to be the “Trigger” and is going to initiate an Action in the other application(s)

 

In the App Event window, enter “One Click Contractor” in the “Search Apps” section and        then select “One Click Contractor (###)”

Under “Trigger Event” click the drop down and choose “Job Created or Updated Event” or “Estimate Created or Updated Event” 

  1. Click Continue
  2. You will then need to Sign In to your One Click Contractor Account. Keep in mind that you should only have to do this once and on subsequently created Zaps you can use the saved credentials.

In the popup, enter your email address and password for an “Org Admin Account” or the account that has permissions to the data you need. Once you’ve entered the credentials, click “Yes, Continue”

From the trigger screen, select the newly created account from the dropdown.

 

Once you’ve selected the appropriate account, click Continue

On the next screen, we need to select the appropriate criteria to filter the events.
You will need to select:

  • The selected Organization(s) you want to run this on
  • Whether or not you want it to include all orgs below
Filter the type of event(s) you want to use to trigger this zap

For the option of “Include All Child Orgs” it is recommended to choose “Yes, include all child orgs”

For the Filter, choose the events you would like to use in this zap. The options are:
    1. Job Created: This event is triggered when a Job is Created
    2. Job Updated: This event is triggered when an update happens to a Job. A few examples would be:
      1. Updated Address
      2. Changing a phone number
      3. Updating a name
      4. Etc.
    3. Job User Assignment Changed: This event is triggered when a job is reassigned to a different user.
    4. Job Status Changed: This event is triggered when a job has a status that is changed.
    5. Signable Document: This event is triggered when a job has a signable document which has been fully executed. 
    6. Job Document Created: This event is triggered each time a document is added to the job.

Once you have created the trigger, you can Test the trigger by clicking “Test trigger” which will pull a job record from your One Click to validate things are working appropriately.

Once you see the data show up, you can click “Continue”

Now that the trigger has been configured appropriately, you’re ready to set up the Action. This is the actual update that is going to happen as a result of the Trigger we set up. A few examples would be:

  1. Create/Update a Customer in QuickBooks when a job is created/updated.
  2. The steps to complete that will be based on the app you’re connecting to. For more information and the availability of those, please reference the developer of that application and Zapier for more information.

Other available Triggers and Events:

  • Estimate Created or Updated:
    • Estimate Created: This event is triggered each time an estimate is created for a job.
    • Estimate Updated: This event is triggered each time an estimate is updated.
    • Signed Document: This event is triggered when a signed document is fully executed by all parties.
    • Estimate Manual Trigger: This event is triggered manually by a user on a saved estimate in the platform. 

Step 2b: Make a Zap (One Click Contractor as Action)

If you’ve already started creating a zap, and have used a trigger from another platform as your Trigger, you can set a Create Job Action in One Click Contractor.

  1. When you get to the Action step after setting up your Trigger, choose “One Click Contractor”

Under Action, Choose “Create Job”

If necessary, log into your One Click Contractor Account as described in section 2A.

Click Continue

  1. Next, you’ll tell the Zap what sections of the One Click Contractor Job you’ll want populated from your Trigger platform. Click the plus sign next to each field you’d like populated to choose a corresponding field from your Trigger platform. When your mapping is complete, click Continue.

Below are the Job attributes that can be populated via the zap:

 Job:

“Customer Name” (only required attribute)

“Email”

“Job Name” (if empty, this will default to the Customer Name)

“Lead Source”

“Job Types”

Job Address:

“Address Line 1”

“Address Line 2”

“Address City”

“Address State”

“Address Postal Code”

“Address Country”

Customer Address:

“Customer Address Line 1”

“Customer Address Line 2”

“Customer Address City”

“Customer Address State”

“Customer Address Postal Code”

“Customer Address Country”

Phone Number:

“Phone Name”

“Phone Number”

Appointment (only 1 appointment can be created):

“Appointment Start Time”

“Appointment End Time” (Note: if there is an appointment Start Time, there must be an End Time)

“Appointment Summary”

“Appointment Description”

“Assigned User”

Now you can test the Zap to make sure the mapping will successfully Create a Job in One Click Contractor.

If successful you’ll see details of the Created Job and have the ability to Publish the Zap and start using it.