Appointment Status Workflow Trigger in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Appointment Status trigger runs a Sparkforge workflow whenever an appointment is created or its status changes. Filter by status, event type, calendar, tag, and who modified the appointment, and choose whether guests get enrolled too.

The Appointment Status trigger fires a workflow whenever an appointment is booked or its status changes. Use it for confirmations, reminders, no-show recovery, internal alerts, and team handoffs without manual work.

What it covers

Status changes: New, Confirmed, Cancelled, Showed, No-show, Invalid.
Multi-participant: enroll the primary contact, the guests, or both.
Filters by calendar, calendar group, tag, event type, and who modified the appointment.

Add the trigger

Go to Automation → Workflows and create or edit a workflow.
Click Add New Trigger and search for Appointment Status.
Select it.

Name the trigger

Use a descriptive name so the workflow stays readable: “Appointment Follow-Up”, “Cancellation Alert”, “No-Show Recovery”. Default “Appointment Status” names get hard to maintain at scale.

Choose enrollment

Under Who should be enrolled into the workflow?, pick:

Contact only — default; only the primary appointment contact.
Contact and Guests — primary plus all guest contacts. The workflow runs once per person.
Guests only — guests only; primary excluded.

For a cancellation notice, Contact and Guests is usually right.

Filters

Event Type

Any, Normal (non-recurring), or Recurring.

Appointment Status

New, Confirmed, Cancelled, Showed, No-show, Invalid.

Tag

Restrict the trigger to contacts that carry a specific tag — useful for segmenting VIPs or particular service lines.

In Calendar

Limits the trigger to one specific calendar.

In Calendar Group

Limits the trigger to a calendar group, useful when teams or service categories share a group.

Only for Grouped Calendar

Yes restricts to grouped calendars only. No covers both grouped and individual calendars.

Modified By

API — status changed via API.
Customer — the client made the change.
User — a CRM user changed it; you can pick a specific user in the next step.
Workflow — another workflow modified the status.

Save and test

Save the trigger, save the workflow, then publish. Book or update an appointment to confirm the workflow runs as expected.

Frequently Asked Questions

Does rescheduling fire the trigger again?

Yes. Rescheduling is treated as a new appointment, so the contact re-enters the workflow from the start.

How does the Modified By filter work?

It scopes the trigger to who changed the status — API, customer, user, or another workflow. Pick User to restrict further to a specific CRM user.

What’s the difference between In Calendar and In Calendar Group?

In Calendar targets one specific calendar. In Calendar Group targets every calendar inside a named group, which is the right choice when teams share scheduling.

Can I combine multiple filters?

Yes. Filters compose with AND/OR conditions, so you can narrow the trigger to, say, Cancelled status, in a specific calendar group, modified by Customer.

If I pick Contact and Guests, does the workflow run once or per person?

Once per person. Each guest gets an independent execution, so contact-specific custom values resolve correctly in messages.