The Zapier & Jetpack Workflow uses simple filtering to determine what Jobs to create in Jetpack Workflow.

In this example, we are going to use a Data Utility in our Zap to help add some more variability into our connection. This configuration works best if you are using each service in Ignition to create a singular Job in Jetpack.

Building a Lookup Table to map services to job templates

Next, we want to build our table. The left-hand column (input) of the table is your Ignition Service Names. The right-hand column (output) of the table is the unique ID for your matching Jetpack Template.

Note: You can find your unique Jetpack template IDs by opening a Create Job Action:

Format the contact name by using the Split Text action below.

Then, find Contact in Jetpack Workflow.

Note: if you have both Personal and Business clients: Build in a couple of Paths here with conditional logic so personal jobs look up a person and business jobs look up a business and subsequently create the Job under the proper contact. The rest of the Zap has the same basic setup.

As with the last, we create this will use a Lookup Table to translate the Manager in Ignition to the Manager in Jetpack using the unique ID for the Users in Jetpack:

Again if you are not aware of what your ID is in Jetpack you can use a Create Job action and check it out:

Then, create our Job based on the service accepted and assign it to the Manager:

Click here for a Advanced Jetpack Zap template using Data Utility.

Note that you will have to customize this Zap for your own circumstances.