Practical examples
Use these recipes as starting points for automating scheduling workflows with the Dime.Scheduler Zapier connector. Each example shows the trigger, the action, the field mapping, and the kind of customer scenario it fits.
Appointments from Google Calendar events
Scenario: Automatically create appointments in Dime.Scheduler when events are added to a specific Google Calendar.
Trigger
App: Google Calendar
Event: New Event
Action
App: Dime.Scheduler
Event: Create or Update Item
Item Type: Appointment
Field mapping
| Google Calendar Field | Dime.Scheduler Field | Notes |
|---|---|---|
| Summary | subject | Event title |
| Description | body | Event description |
| Start Time | start | Start date/time |
| End Time | end | End date/time |
| Calendar Name | sourceApp | Use "Google Calendar" |
| Event ID | appointmentNo | Unique identifier |
Configuration
Source App: Google Calendar
Source Type: Calendar Event
Job No: [Set a default or map from event]
Task No: [Set a default or map from event]
Resource No: [Extract from event description or set default]
Subject: {{summary}}
Body: {{description}}
Start: {{start_time}}
End: {{end_time}}
Importance: 1
Why you would build this
This fits organizations that book customer appointments through Google Calendar and want those bookings reflected in Dime.Scheduler for resource planning, without re-entering anything by hand.
Tasks from Asana
Scenario: When a new task is created in Asana, create a corresponding task in Dime.Scheduler.
Trigger
App: Asana
Event: New Task
Action
App: Dime.Scheduler
Event: Create or Update Item
Item Type: Task
Field mapping
| Asana Field | Dime.Scheduler Field | Notes |
|---|---|---|
| Task Name | shortDescription | Brief title |
| Task Notes | description | Detailed description |
| Task ID | taskNo | Unique identifier |
| Project ID | jobNo | Link to job |
| Assignee Email | Use to lookup resourceNo | May require intermediate step |
| Due Date | requestedEndDate | Deadline |
| Priority | importance | Map to 0-2 scale |
Configuration
Source App: Asana
Source Type: Task
Job No: {{project_id}}
Task No: {{task_id}}
Short Description: {{task_name}}
Description: {{notes}}
Category: {{project_name}}
Importance: {{priority}} (mapped: High=2, Medium=1, Low=0)
Requested Start Date: {{start_date}}
Requested End Date: {{due_date}}
Handling the assignee lookup
Create a lookup table in Airtable or Google Sheets to map Asana assignee emails to Dime.Scheduler resource numbers. Add a "Lookup" step before the Dime.Scheduler action.
Notify a resource when their appointment changes
Scenario: Send an email or SMS notification to the assigned resource when their appointment is modified.
Trigger
App: Dime.Scheduler
Event: Updated Appointment
Action 1
App: Formatter by Zapier
Event: Date/Time Format
Purpose: Convert appointment times to readable format
Action 2
App: Email by Zapier (or Twilio for SMS)
Event: Send Email
Field mapping
| Dime.Scheduler Field | Email Field | Notes |
|---|---|---|
resourceName | To Name | Who receives the email |
| Look up resource email | To Email | May require lookup step |
subject | Email Body | Part of message |
start | Email Body | Formatted start time |
end | Email Body | Formatted end time |
jobName | Email Body | Job details |
Email template
Subject: Your appointment has been updated
Hi {{resourceName}},
Your appointment "{{subject}}" has been updated with the following details:
Job: {{jobName}}
Task: {{taskName}}
Start Time: {{formatted_start}}
End Time: {{formatted_end}}
Location: {{siteAddress}}
Please confirm receipt of this update.
Best regards,
Scheduling Team
Why you would build this
Keep field technicians, sales reps, or service personnel informed of schedule changes in real time, with no manual notifications to send.
Making these hold up in production
The examples above are deliberately minimal. A few habits are what separate a Zap that survives contact with real data from one that quietly stops working.
Start with one Zap and get it reliable before chaining more onto it. Debugging two interacting Zaps is more than twice the work of debugging one.
Name Zaps for what they do. "Create DS appointment from Salesforce opportunity" tells the next person what breaks if they disable it. "Salesforce to DS" does not.
Always populate sourceApp and sourceType. They are what records where the data came from and what lets Dime.Scheduler recognise the same record on the next run. This is the single most common omission, and it fails quietly: the Zap succeeds and the record is either invisible or duplicated on every update.
Decide what happens in the awkward cases before they happen rather than after. Required data missing from the source, dates arriving in an unexpected time zone, a record that already exists, a parent record that does not exist yet. Each of these is a filter or a lookup step, and each is much cheaper to add now than to diagnose from a Zap history in three months.
Check the Zap history weekly and turn on failure notifications. Zaps fail silently by design: the workflow simply stops, and nobody downstream necessarily notices that appointments stopped arriving.
Read more
- Actions and triggers
- Source app and source type, the two fields the advice above keeps returning to
- Troubleshooting