Triggers

Triggers allow you to start Zaps when specific events occur in Dime.Scheduler. The connector provides real-time webhook-based triggers that fire instantly when changes occur.

New Appointment

Trigger: newAppointment
Description: Fires when a new appointment is created in Dime.Scheduler.

Output Fields

The trigger provides the following appointment data:

Field	Type	Description
id	string	Unique identifier for the appointment
appointmentNo	string	Human-readable appointment number
appointmentGuid	string	Global unique identifier
jobNo	string	Associated job number
taskNo	string	Associated task number
resourceNo	string	Assigned resource number
subject	string	Appointment subject/title
body	string	Appointment description/notes
start	datetime	Appointment start date and time
end	datetime	Appointment end date and time
importance	integer	Importance level (0=Normal, 1=High, 2=Low)
locked	boolean	Whether the appointment is locked
planningQuantity	string	Planning quantity for the appointment
unitOfMeasure	string	Unit of measure (e.g., "H" for hours)
createdAt	datetime	When the appointment was created
updatedAt	datetime	When the appointment was last modified

Use Cases

• Send notifications when appointments are scheduled
• Create calendar events in Google Calendar or Outlook
• Log appointment details to a spreadsheet
• Trigger customer notifications via email or SMS

---

Updated Appointment

Trigger: updatedAppointment
Description: Fires when an existing appointment is modified in Dime.Scheduler.

Output Fields

Same fields as New Appointment, with updatedAt reflecting the modification time.

Use Cases

• Notify resources when appointments are rescheduled
• Update external calendar systems
• Track appointment changes in a database
• Send update notifications to customers

---

Removed Appointment

Trigger: removedAppointment
Description: Fires when an appointment is deleted or removed from Dime.Scheduler.

Output Fields

Same fields as New Appointment, plus:

Field	Type	Description
deletedAt	datetime	When the appointment was deleted

Use Cases

• Cancel calendar events in external systems
• Notify stakeholders of cancellations
• Archive deleted appointment data
• Trigger refund or rebooking workflows

---

Best Practices

Working with Triggers

Filter Early: Use Zapier's Filter step to only process appointments that meet specific criteria (e.g., specific categories, importance levels, or resources).

Handle Duplicates: Although unlikely, implement deduplication logic in your Zaps if you're concerned about the same event triggering multiple times.

Map Data Carefully: Ensure you understand which fields are available from the trigger before building your Zap's actions.

Using Appointment Data

Identifiers: The trigger provides multiple identifiers (appointmentId, appointmentNo, appointmentGuid). Use the one that best fits your integration needs:

• Use appointmentGuid for external system references
• Use appointmentNo for human-readable references
• Use id for internal Dime.Scheduler operations

Date/Time Handling: All datetime fields are in ISO 8601 format. Zapier automatically converts these for use in other apps, but be aware of timezone considerations.

Performance

Instant Triggers: All appointment triggers are webhook-based, meaning they fire within seconds of the event occurring in Dime.Scheduler.

Rate Limits: While triggers themselves are instant, be mindful of rate limits on downstream actions (e.g., API calls to other services).