Zapier connector
Most customers need Dime.Scheduler to talk to something the standard connectors do not target: a CRM, a form builder, a chat tool, a spreadsheet. Building that integration properly means an API client, a deployment, and someone to maintain it. The Zapier connectorConnectorAn integration that links Dime.Scheduler to a back-office system, routing data in and scheduling decisions back out. is the answer when that cost is out of proportion to the problem.
It puts Dime.Scheduler on the Zapier platform alongside several thousand other applications, so an integration becomes a workflow you configure rather than software you write. The connector is publicly listed: search for Dime.Scheduler when creating a Zap, with no invitation needed.
What travels in each direction
The connector works both ways, but not symmetrically, and the asymmetry is the first thing to design around.
Into Dime.Scheduler, the connector is broad. It creates and updates appointmentsAppointmentA task scheduled to a resource for a specific period - the scheduled instance you see on the planning board., tasksTaskA unit of work that belongs to a job. It appears in the open task list until it is scheduled to a resource., resourcesResourceAn entity that can carry out work - a person, vehicle, tool, or room - that you schedule on the planning board., jobsJobA high-level container, comparable to a project, that bundles related tasks together with common information such as customer, billing, and address., categoriesCategoryA visual indicator (a color) applied to appointments to classify or label them., time markers, pins, containers, assignments, notifications, action URLs, captions, filter groups and filter values: seventeen item types in all. It can also set individual attributes on an existing record without recreating it, and delete records.
Out of Dime.Scheduler, it is narrow. Three triggers, and all three are about appointments: created, updated, and removed. There is no trigger for a change to a task or a resource. If your workflow needs to react to one of those, Zapier is not the tool and the webhook connector is.
The triggers are webhook-based rather than polled, so they fire within seconds rather than on a schedule. Each one delivers the full appointment payload, including job details, resource information, timing and custom fields, which usually saves a follow-up lookup to enrich the data.
How it fits together
A Zap is a trigger plus one or more actions. Something happens in a source application, Zapier captures it, maps the fields to what the target expects, and the connector calls the Dime.Scheduler API to create, update or delete. The reverse runs the same way with a Dime.Scheduler appointment as the trigger.
Everything the connector does goes through the same public REST API you could call yourself. Zapier is a hosted client for it, not a separate integration path, so anything the connector can do is also available to code, and anything it cannot do is generally not a Zapier limitation.
Authentication and environments
The connector authenticates with an API key and asks which environment to use. Both sandbox and production are available, and choosing between them is part of setting up the connection rather than a setting you change later.
Build against sandbox. A Zap that loops or duplicates is cheap to discover there and expensive to discover in a live tenant.
What you need
- An active Dime.Scheduler subscription, production or sandbox.
- An API key with the permissions the Zap requires.
- A Zapier account. Free and paid tiers both work; the tier decides how many operations you can run per month.
The connector itself is included with your subscription.
Where this goes wrong
Two failure modes account for most of the support traffic, and both are worth knowing before you build rather than after.
Source app and source type. Records written into Dime.Scheduler carry these two values, and they decide how a record is identified and routed. Get them wrong and the Zap reports success while the record never appears where the planner expects it. See actions for how to set them.
The updated-appointment trigger fires on every change. Every one, including changes nobody cares about. A Zap that notifies a channel on each update gets muted within a week. Put a Zapier filter directly after the trigger to narrow it to the changes that matter.
Where to go next
Start with prerequisites for the accounts and keys, then installation to build the first Zap. Triggers and actions are the reference for what each one carries, examples shows complete workflows, and troubleshooting covers what to do when a Zap does not fire.
For a guided version of the whole thing, see automate notifications with Zapier in the cookbook.