Housecall Pro – More workflow actions & triggers

Based on the response we received we have added a multiple actions and triggers for Housecall Pro.

What’s new?

The Housecall Pro integration in Workflows now spans the full field-service lifecycle. Nine triggers — covering jobs, estimates, leads, and customers — and fourteen actions across customer, job, estimate, lead, and job-appointment management let home service businesses react to operational events and drive Housecall Pro from any workflow.

How it works

All triggers poll Housecall Pro on a fixed cadence: creation events (Job created, Estimate created, Lead created, Customer created) every 5 minutes, and schedule, finish, and cancel events (Job scheduled, Job finished, Job canceled, Estimate scheduled, Estimate finished) every 10 minutes. Actions cover the full CRUD surface for customers and customer addresses, full job and job-appointment management, estimate creation and retrieval, and lead creation and retrieval. Authentication is API key — connect once, target multiple accounts via the Connected Account dropdown.

How to use it

  • In Workflows, add a Housecall Pro trigger or action.
  • Click Connect your account; in the Connect with API Key modal, paste your Housecall Pro API key (Housecall Pro → My Apps → Go to App Store → API Key Management → Generate API Key with Full Access).
  • For triggers: optionally Add filters to scope by customer, tag, employee, or any captured field; then Find new records to capture a sample payload.
  • For actions: fill required fields (varies by action — most need a customer or object ID); Test Action to validate.
  • Save and publish.

Simple example

A homeowner submits a ‘Request a Quote’ form on the website. The workflow creates the matching Housecall Pro lead via Create a lead, pings dispatch with the lead context, and tags the CRM contact. Two days later, the office books an estimate visit — Estimate scheduled fires and the workflow sends the customer a reminder with the technician’s ETA. The technician completes the estimate; Estimate finished fires and the workflow sends the customer a link to review and approve the quote. Once approved, the workflow uses Create a job to spin up the job, and the cycle continues through Job scheduled, Job finished, and the post-service follow-up.

Additional Notes

  • Triggers (9): Job created (5 min), Job scheduled (10 min), Job finished (10 min), Job canceled (10 min), Estimate created (5 min), Estimate scheduled (10 min), Estimate finished (10 min), Lead created (5 min), Customer created (5 min). All polling.
  • Actions (14): Create new customer, Get customer details, Update a customer, Find customers, Get a customer address, Create a customer address, Create a job, Get job details, Create a job appointment, Update a job appointment, Create an estimate, Get an estimate, Create a lead, Get a lead.

Email Services Dashboard for Agencies

New: Email Services Dashboard for Agencies

We've launched a new Email Services dashboard in the Agency UI — giving you full visibility into your domain's sending health and sub-account performance in one place.

What's new:

  • Domain health states — your domain is automatically evaluated and assigned one of six states: Healthy, At Risk, Critical, New, Recovering, or Shared Domain. No manual monitoring required.
  • Key sending metrics — track Delivery Rate, Bounce Rate, Spam Complaint Rate, and Open Rate with clear target thresholds.
  • Domain health history — a timeline showing every upgrade and downgrade event, with details on what triggered each change.
  • Sub-account performance — see all sub-accounts on your shared domain grouped by health status (Healthy / At Risk / Critical). Search by name, click through to any account's individual metrics, and scroll through large account lists seamlessly.

Who this applies to: Agencies created on or after April 27, 2026. Existing agencies are unaffected — a migration plan is coming by end of Q2 2026.

📖 Full guide here

image

Calendly – Workflow Actions & Triggers

What’s new?

You can now connect Calendly directly to Workflows. Five triggers — Invitee created, Invitee canceled, Invitee no show created, New routing form submission, and Event cancelled — plus nine actions covering one-off meeting creation, invitee booking, event lifecycle management, no-show marking, and Calendly contact and user lookups let your automations react to scheduling activity and drive Calendly back the other way.

How it works

Four of the five triggers are instant — backed by Calendly’s native webhooks (invitee.created, invitee.canceled, inviteenoshow.created, routingformsubmission.created). The fifth (Event cancelled, for host-initiated cancellation) polls every 5 minutes because Calendly does not emit a native webhook for it. Each instant trigger exposes a Webhook Subscription Scope filter — User to watch the connected user’s events, or Organization to watch every user in the Calendly org. Authentication is OAuth via an External Authentication Configuration step that labels each connected account with a friendly Name and Email.

How to use it

  • In Workflows, add a Calendly trigger or action.
  • Click Connect your account; enter a friendly Name and Email for the connected account in the External Authentication Configuration modal, then complete the OAuth handshake on Calendly’s side.
  • For instant triggers: pick a Webhook Subscription Scope (User or Organization) and any additional filters.
  • For actions: fill required fields (Event Name, Host User, Duration, Start Date, End Date for Create one-off meeting; identifiers + payload for the rest); Test Action to validate.
  • Save and publish.

Simple example

A prospect books a discovery call through a sales rep’s Calendly link. Invitee created fires within seconds — the workflow finds or creates the matching CRM contact, attaches the booking details (event type, scheduled window, custom question answers) to custom fields, and sends a pre-call SMS with prep material. If the prospect later cancels, Invitee canceled fires; the workflow waits two hours, then sends a tailored reschedule offer with a one-off Calendly link.

Additional Notes

  • Triggers (5): Invitee created (Instant), Invitee canceled (Instant), Invitee no show created (Instant), New routing form submission (Instant), Event cancelled (Polling 5 Mins for host-initiated cancellation since Calendly has no native webhook for it).
  • Actions (9): Create one-off meeting, Book meeting for invitee, Find event, Cancel an event, Mark invitee as no show, Create contact, Find contact, Update contact, Find user.
  • OAuth authentication via the External Authentication Configuration modal — each connected account is labeled with a Name and Email for clear multi-account routing.
  • Webhook Subscription Scope filter on instant triggers — pick User for individual rep automations or Organization for shared sales/CS workflows.
  • Create one-off meeting accepts Duration up to 720 minutes (12 hours); Timezone defaults to the host’s time zone and accepts IANA names (America/New_York, Asia/Kolkata).
  • A reschedule in Calendly appears as two events in this integration — invitee.canceled for the old slot followed by invitee.created for the new slot.

Calendly – Workflow Actions & Triggers

What’s new?

You can now connect Calendly directly to Workflows. Five triggers — Invitee created, Invitee canceled, Invitee no show created, New routing form submission, and Event cancelled — plus nine actions covering one-off meeting creation, invitee booking, event lifecycle management, no-show marking, and Calendly contact and user lookups let your automations react to scheduling activity and drive Calendly back the other way.

How it works

Four of the five triggers are instant — backed by Calendly’s native webhooks (invitee.created, invitee.canceled, inviteenoshow.created, routingformsubmission.created). The fifth (Event cancelled, for host-initiated cancellation) polls every 5 minutes because Calendly does not emit a native webhook for it. Each instant trigger exposes a Webhook Subscription Scope filter — User to watch the connected user’s events, or Organization to watch every user in the Calendly org. Authentication is OAuth via an External Authentication Configuration step that labels each connected account with a friendly Name and Email.

How to use it

  • In Workflows, add a Calendly trigger or action.
  • Click Connect your account; enter a friendly Name and Email for the connected account in the External Authentication Configuration modal, then complete the OAuth handshake on Calendly’s side.
  • For instant triggers: pick a Webhook Subscription Scope (User or Organization) and any additional filters.
  • For actions: fill required fields (Event Name, Host User, Duration, Start Date, End Date for Create one-off meeting; identifiers + payload for the rest); Test Action to validate.
  • Save and publish.

Simple example

A prospect books a discovery call through a sales rep’s Calendly link. Invitee created fires within seconds — the workflow finds or creates the matching CRM contact, attaches the booking details (event type, scheduled window, custom question answers) to custom fields, and sends a pre-call SMS with prep material. If the prospect later cancels, Invitee canceled fires; the workflow waits two hours, then sends a tailored reschedule offer with a one-off Calendly link.

Additional Notes

  • Triggers (5): Invitee created (Instant), Invitee canceled (Instant), Invitee no show created (Instant), New routing form submission (Instant), Event cancelled (Polling 5 Mins for host-initiated cancellation since Calendly has no native webhook for it).
  • Actions (9): Create one-off meeting, Book meeting for invitee, Find event, Cancel an event, Mark invitee as no show, Create contact, Find contact, Update contact, Find user.
  • OAuth authentication via the External Authentication Configuration modal — each connected account is labeled with a Name and Email for clear multi-account routing.
  • Webhook Subscription Scope filter on instant triggers — pick User for individual rep automations or Organization for shared sales/CS workflows.
  • Create one-off meeting accepts Duration up to 720 minutes (12 hours); Timezone defaults to the host’s time zone and accepts IANA names (America/New_York, Asia/Kolkata).
  • A reschedule in Calendly appears as two events in this integration — invitee.canceled for the old slot followed by invitee.created for the new slot.

Calendly – Workflow Actions & Triggers

What’s new?

You can now connect Calendly directly to Workflows. Five triggers — Invitee created, Invitee canceled, Invitee no show created, New routing form submission, and Event cancelled — plus nine actions covering one-off meeting creation, invitee booking, event lifecycle management, no-show marking, and Calendly contact and user lookups let your automations react to scheduling activity and drive Calendly back the other way.

How it works

Four of the five triggers are instant — backed by Calendly’s native webhooks (invitee.created, invitee.canceled, inviteenoshow.created, routingformsubmission.created). The fifth (Event cancelled, for host-initiated cancellation) polls every 5 minutes because Calendly does not emit a native webhook for it. Each instant trigger exposes a Webhook Subscription Scope filter — User to watch the connected user’s events, or Organization to watch every user in the Calendly org. Authentication is OAuth via an External Authentication Configuration step that labels each connected account with a friendly Name and Email.

How to use it

  • In Workflows, add a Calendly trigger or action.
  • Click Connect your account; enter a friendly Name and Email for the connected account in the External Authentication Configuration modal, then complete the OAuth handshake on Calendly’s side.
  • For instant triggers: pick a Webhook Subscription Scope (User or Organization) and any additional filters.
  • For actions: fill required fields (Event Name, Host User, Duration, Start Date, End Date for Create one-off meeting; identifiers + payload for the rest); Test Action to validate.
  • Save and publish.

Simple example

A prospect books a discovery call through a sales rep’s Calendly link. Invitee created fires within seconds — the workflow finds or creates the matching CRM contact, attaches the booking details (event type, scheduled window, custom question answers) to custom fields, and sends a pre-call SMS with prep material. If the prospect later cancels, Invitee canceled fires; the workflow waits two hours, then sends a tailored reschedule offer with a one-off Calendly link.

Additional Notes

  • Triggers (5): Invitee created (Instant), Invitee canceled (Instant), Invitee no show created (Instant), New routing form submission (Instant), Event cancelled (Polling 5 Mins for host-initiated cancellation since Calendly has no native webhook for it).
  • Actions (9): Create one-off meeting, Book meeting for invitee, Find event, Cancel an event, Mark invitee as no show, Create contact, Find contact, Update contact, Find user.
  • OAuth authentication via the External Authentication Configuration modal — each connected account is labeled with a Name and Email for clear multi-account routing.
  • Webhook Subscription Scope filter on instant triggers — pick User for individual rep automations or Organization for shared sales/CS workflows.
  • Create one-off meeting accepts Duration up to 720 minutes (12 hours); Timezone defaults to the host’s time zone and accepts IANA names (America/New_York, Asia/Kolkata).
  • A reschedule in Calendly appears as two events in this integration — invitee.canceled for the old slot followed by invitee.created for the new slot.