Triggers

Triggers start a Zap the moment something happens in Dime.Scheduler. The connector uses real-time webhooks, so each trigger fires within seconds of the event. This page lists the available triggers, the data each one returns, and how to put them to work.

New Appointment

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

Output Fields

The trigger returns 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: Add Zapier's Filter step so the Zap only processes appointments that meet your criteria (for example, specific categories, importance levels, or resources).

Handle duplicates: Although unlikely, add deduplication logic to your Zaps if you are concerned about the same event firing more than once.

Map data carefully: Check which fields the trigger provides before you build the Zap's actions.

Using Appointment Data

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

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

Date and time handling: All datetime fields use the ISO 8601 format. Zapier converts these automatically for use in other apps, but watch for timezone differences.

Performance

Instant triggers: Every appointment trigger is webhook-based, so it fires within seconds of the event in Dime.Scheduler.

Rate limits: Triggers themselves are instant, but keep an eye on rate limits for downstream actions such as API calls to other services.