How to create a detailed event in Google Calendar for a specific technician in ServiceTitan

Hi ​@PaintItUp 

For us to have more info, post these screenshots:

• how your Zap steps are outlined
• how your Zap steps are configured in EDIT mode with the field mappings visible

Thanks Troy...pretty new with Zapier….Hopefully I post what is needed.

This was working fine when we only had one calendar to contend with but when we added a second one it seems that neither Step 1 nor Step 4 filter out other technicians.

​@PaintItUp 

Help links for using Filters/Paths in Zaps:

• Filter: https://zapier.com/apps/filter/integrations#help
• Paths: https://zapier.com/apps/paths/integrations#help

​@Troy Tessalone 

So I had created a Filter and moved it to several location but still didn’t filter out incorrect technicians and instead it put it on all calendars. I did move it from Step 2 to Step 3 and then Step 4 with all the same results. It seems to ignore the False statement

I did start the process off with New Appointment and chose Technician specific to Dee_K.

I then left the Filter Condition and added a Path, which still didn’t garner the results I wanted, so I removed the Filter Step entirely using only the Path Steps. Each Path Step (5, 7, 9)

I then moved the Path to a more up front decision tree but I can’t figure out how to make the Path Conditional on each Technical ID. They don’t seem to be available as an option.

I’m sure I missing some simple statement but just not finding it. Any troubleshooting advise.

Bob

​@PaintItUp 

What data point returned from a Zap step before a Path Filter step indicates the Technician Name or Technician ID?

Post screenshots showing the DATA OUT returned from the Zap step that shows the Technician.

These are the details available after selecting New Appointment. When I added a specific technician I thought it would drive the entire set of steps around only that technician so I left it null, I did try it by selecting a specific tech id (as shown in the second example) but that seemed to have no affect.

I was hoping that null would bring the values forward and allow the path conditions to work for each technician.

​@PaintItUp 

Options to try:

• If you select a Technician in the Zap trigger step, then the Zap trigger step should only return data for that Technician.
• If you do not select a Technician in the Zap trigger step, then the Zap trigger should include all Technicians
  • The Technician ID should be returned, which you can use in a Path Filter step as part of the condition
  • We would need to see screenshots showing how your Zap Path Filter step conditions are configured

So this is what I’m given for the Path Conditions…

 and when I search for Technician, it comes back with nothing

​@PaintItUp 

You can try adding this Zap step to lookup the Appointment to see if that returns the info about the Technician.

Zap action: ServiceTitan - Search Appointments

Would that step be added as #2 or is this the way I should begin this whole zap? I’ve tried to use it as Step #2 and it won’t come up as a option.

​@PaintItUp 

This is an action step, so it can only be added as Zap Step 2+.

Zap action: ServiceTitan - Search Appointments

You would want to add this as Zap step 2.

Then if the step returns info about the Technician, you can use that in the Filter conditions.

It’s not coming up as an option. Should I be using a different version other than 2.0.19?

​@PaintItUp 

From your screenshot...

Zap action: ServiceTitan - Find Appointment

Description: Finds an Appointment by the ID

And then I get no options.

Ok, by changing this step to ServiceTitan (3.0.14) I have found Search Appointments and it does show Techician ID. I leave it null, and go to Path A to apply a condition I’m not sure what I should select to proceed to the next step for finding a technician or perhaps even creating a condition to choose this path.

Hi there, ​@PaintItUp 👋

Hope you don’t mind me jumping in here! If the Search Appointments action outputs the Technician ID for the appointment then you use the Exists or Does not exists rule conditions for the paths. Those conditions could be used to determine whether a value exists or doesn’t exist for the Technician ID and allow the path to run accordingly.

Alternatively, if you want different paths to run for different technicians then you could use the (Text) Exactly matches condition for the path to see if the value in the Technician ID matches a specific value.

You can learn more about the different path conditions here: Filter and path rules in Zaps

Hope that helps to get you pointed in the right direction. If you run into any further issues or questions just let us know! 🙂

​@SamB thanks for jumping in…. Here’s my …

When I open Search Appointments, Technician ID exists:

But when I go to create a condition for the 6. Path conditions (assuming I use “Custom rules”), it doesn’t and therefore I can’t choose the Exists or Does not exists rule condition.

Argh….

Thanks for getting back to me, ​@PaintItUp. 🙂

Looking at your screenshots it seems it’s only showing ids for the available technicians in that Technician ID field, which is used to narrow the search to appointments associated with a specific technician. I checked the action on this end and it doesn’t output the technician ID for the appointment, so you wouldn’t be able to select that when setting up the paths. This means that we need another search action that will give the technician ID so that we can reference it in the paths.

It did some checking on this end and it seems the Search Appointment Assignments action would output the Technician ID. To use that action you would search for the appointment assignment using the Appointments ID that is output by the previous Search Appointment action:

Then, in the paths you would be ablt to check the TechnicianId field (that’s output by the Search Appointment Assignments action) to see if it exists or not. 

Can you give that a try and let us know how it goes?

​@SamB It appears to be stepping through correctly now but I have an issue where Step 3 is consistantly providing data out and specifically Technician Name as Dee_K and therefore only providing results for Path A. There should be no reason where the Technician is being selected until the Path condition in Step 10 which is where I set it up as Exists As “Dee_K”.