Actions

Where triggers are narrow, actions are broad. They push data into Dime.Scheduler from the other apps in your Zap, covering seventeen item types across three verbs: create or update, set a single attribute, and delete.

Which verb you want depends on what you know about the record. Create or update is the workhorse when the record may or may not exist yet. Set attribute changes one property on something that definitely exists, without resupplying the rest of it. Delete removes it.

Create or update item

createOrUpdateItem is the main action for managing scheduling data. It creates the record if it does not exist and updates it if it does, which is decided by the source app, source type, and identifier you supply.

Supported item types

Item Type	Description
Appointment	Scheduled time slots assigned to resources
Task	Work items with job details and scheduling information
Resource	People, vehicles, or equipment that can be scheduled
Job	Collections of tasks (projects or work orders)
Category	Organizational classifications for tasks, jobs, or resources
Time Marker	Time period markers for scheduling and tracking
Pin	Important location or item markers
Container	Groups for organizing related tasks or appointments
Assignment	Resource assignments to appointments
Notification	Alerts and messages for users or resources
Action URL	Links to external resources or systems
Caption	Custom labels and descriptions in different languages
Filter Group	Filter option organizers
Filter Value	Individual filter values for data filtering

Appointment

Create or update complete appointments, including their scheduling details.

Key fields:

Field	Type	Description
sourceApp	string	Source application name
sourceType	string	Source type identifier
jobNo	string	Job number
taskNo	string	Task number
resourceNo	string	Resource to assign
subject	string	Appointment title
body	string	Description
start	datetime	Start date/time
end	datetime	End date/time
category	string	Category name
timeMarker	string	Time marker
importance	integer	0=Normal, 1=High, 2=Low
locked	boolean	Lock the appointment

Example Use Case: Create appointments from CRM opportunities, customer bookings, or project management tools.

Task

Create or update tasks, along with their job details and scheduling information.

Key fields:

Field	Type	Required	Description
sourceApp	string	✓	Source application
sourceType	string	✓	Source type
jobNo	string	✓	Parent job number
taskNo	string	✓	Task number
shortDescription	string	✓	Brief description
description	string		Detailed description
category	string		Task category
timeMarker	string		Time marker
duration	string		Expected duration
importance	string		Task priority
status	string		Current status
requestedStartDate	datetime		Requested start
requestedEndDate	datetime		Requested end

Example Use Case: Import tasks from project management systems, ticketing systems, or field service applications.

Resource

Create or update resources, including their contact information, skills, and availability.

Key fields:

Field	Type	Required	Description
resourceNo	string	✓	Resource identifier
sourceApp	string		Source application
sourceType	string		Source type
resourceName	string		Full name
displayName	string		Display name
email	string		Email address
phone	string		Phone number
mobilePhone	string		Mobile number
department	string		Department
teamCode	string		Team identifier
homeAddress	string		Home address
homeAddressGeoLat	string		Latitude
homeAddressGeoLong	string		Longitude

Example Use Case: Sync employee data from HR systems, manage field technician profiles, or update resource information from Active Directory.

Job

Create or update jobs, including their customer information and project specifications.

Key fields:

Field	Type	Description
sourceApp	string	Source application
sourceType	string	Source type
jobNo	string	Job number
shortDescription	string	Brief description
description	string	Detailed description
name	string	Job name
category	string	Job category
customerNo	string	Customer number
customerName	string	Customer name
customerAddress	string	Customer address
customerPhone	string	Contact phone
customerEmail	string	Contact email
siteAddress	string	Work site address
siteAddressGeoLat	string	Latitude
siteAddressGeoLong	string	Longitude
importance	string	Priority level
startDate	datetime	Planned start
endDate	datetime	Planned end

Example Use Case: Import work orders from ERP systems, create jobs from CRM sales orders, or sync project data.

Category

Create or update categories to organize and classify tasks, jobs, or resources.

Key fields:

Field	Type	Description
name	string	Category name
displayName	string	Display name
color	string	Color code (e.g., "#FF5733")

Example Use Case: Organize work types, prioritize tasks, or create visual distinctions in the scheduler.

Time Marker

Create or update time markers for scheduling and time tracking.

Key fields:

Field	Type	Description
name	string	Time marker name
color	string	Color code

Example Use Case: Mark special time periods, holidays, or shift types.

Pin

Create or update pins to mark important locations, tasks, or resources.

Key fields:

Field	Type	Description
name	string	Pin name
color	string	Pin color

Example Use Case: Highlight priority items, mark VIP customers, or flag urgent tasks.

Container

Create or update containers to group and organize related tasks or appointments.

Key fields:

Field	Type	Description
name	string	Container name
handleDate	string	Date handling settings
handleLocked	string	Lock handling settings

Example Use Case: Group related work items, organize project phases, or batch similar tasks.

Assignment

Create or update resource assignments to appointments.

Key fields:

Field	Type	Description
sourceApp	string	Source application
sourceType	string	Source type
appointmentId	string	Appointment identifier
resourceNo	string	Resource to assign
appointmentGuid	string	Appointment GUID

Example Use Case: Assign resources to work, manage multi-resource appointments, or handle resource changes.

Notification

Create or update notifications to send alerts and messages.

Key fields:

Field	Type	Description
sourceApp	string	Source application
sourceType	string	Source type
appointmentId	integer	Associated appointment
type	integer	Notification type
code	string	Notification code
text	string	Message text
date	string	Notification date

Example Use Case: Send alerts for appointment changes, notify about urgent tasks, or communicate with field workers.

Action URL

Create or update action URLs to link external resources.

Key fields:

Field	Type	Required	Description
sourceApp	string	✓	Source application
sourceType	string		Source type
uriType	string		URI type
uri	string		The URL
description	string		URL description
requestType	integer		Request type
default	boolean		Set as default

Example Use Case: Link to external documentation, connect to back-office systems, or provide quick access to related information.

Caption

Create or update captions for custom labels in different languages.

Key fields:

Field	Type	Description
context	string	Context
sourceTable	string	Source table name
fieldName	string	Field name
language	string	Language code
text	string	Caption text

Example Use Case: Provide multi-language support, customize field labels, or localize the interface.

Filter Group

Create or update filter groups to organize filter options.

Key fields:

Field	Type	Description
name	string	Filter group name
columnNo	string	Column number
dataFilter	string	Data filter expression

Example Use Case: Organize filtering options, create custom views, or categorize data.

Filter Value

Create or update filter values for data filtering.

Key fields:

Field	Type	Description
group	string	Parent filter group
value	string	Filter value

Example Use Case: Define filter options, create selection lists, or organize data hierarchies.

Set attribute

Action: setAttribute
Description: Sets or updates a specific attribute on an existing appointment, task, or resource. Reach for this when you want to change a single property without touching the rest of the item.

Appointment

Category

Assign a category to an appointment

Container

Add appointment to a container

Content

Update subject and/or body text

Importance

Set importance level (0-2)

Locked

Lock or unlock the appointment

Planning quantity

Update planning quantity

Time Marker

Assign a time marker

URI

Add or update a link

Task

Container

Assign task to a container

Filter value

Add filter value to task

Locked

Lock or unlock the task

URI

Add or update a task link

Resource

Calendar

Assign working calendar

Capacity

Set resource capacity

Filter value

Add filter value to resource

Location

Update GPS tracking location

URI

Add or update a resource link

Example Use Cases:

• Lock appointments after confirmation
• Update appointment categories based on status
• Set resource locations from GPS tracking apps
• Update importance levels based on external triggers

Delete item

Action: deleteItem
Description: Permanently removes items from Dime.Scheduler. This operation cannot be undone, so handle it with care.

Warning

Deletion is permanent. Deleted items cannot be recovered. Use with caution.

Supported delete operations

The following item types can be deleted:

• Appointment Container - Remove container assignment
• Category - Delete a category
• Container - Remove container (ungroups items)
• Filter Group - Delete filter group
• Filter Value - Remove filter value
• Job - Delete job (removes all tasks and appointments)
• Notification - Remove notification
• Pin - Delete pin
• Resource - Delete resource (removes all assignments)
• Resource Calendar - Remove calendar assignment
• Resource Filter Value - Remove filter value from resource
• Task - Delete task and associated data
• Task Container - Remove task container assignment
• Task Filter Value - Remove filter value from task
• Time Marker - Delete time marker

Deletions are worth treating more carefully than creates. A Zap that mirrors deletions from another system will remove planned work here, and the appointment a planner spent the morning arranging is gone with it. Filter deliberately, and test against sandbox.

Getting source app and source type right

Most actions require sourceApp and sourceType. Together they record where a record came from, and they are what Dime.Scheduler uses to route it and to recognise it again on the next update.

• sourceApp names the system, for example SALESFORCE or CUSTOM CRM.
• sourceType names the kind of record, for example OPPORTUNITY or WORKORDER.

This is the single most common thing to get wrong. Set the pair inconsistently and the Zap still reports success, but the record is either invisible where the planner expects it or created afresh each run instead of updating the existing one. Choose a pair per integration, write it down, and reuse it everywhere in that Zap.

Choosing an identifier

Appointments, tasks and resources each carry three identifiers, and they are not interchangeable:

• The GUID is globally unique and stable, so it is the one to store in an external system.
• The number, such as appointmentNo or taskNo, is the human-readable reference for anything a person will read.
• The ID is Dime.Scheduler's internal identifier, for operations back against Dime.Scheduler.

Order matters

References must exist before the things that point at them. A job before its tasks, a filter group before its values, an indicator before you assign it.

A Zap that creates a task and its job in the wrong order fails with an error that reads like a validation or permissions problem, which sends people looking in the wrong place. If an action fails on a field that looks correct, check whether its parent exists yet.

Formats

Every datetime field uses ISO 8601: YYYY-MM-DDTHH:mm:ssZ, for example 2025-10-07T14:30:00Z. Zapier converts between formats automatically, but the data still has to reach it in a standard form, and time zones are worth checking rather than assuming.

Booleans and numbers are similarly strict. A field arriving as the string "yes" where a boolean is expected fails validation.

When an action fails

The Zap history carries the actual error message, so start there rather than guessing. Then work down the likely causes in order: a required field that is empty, a value in the wrong format, a reference whose parent does not exist yet, and finally an API key that has expired or been revoked.