Automate with Zapier

The FaciliPulse Zapier integration starts a Zap when a facility or area status update is broadcast. You can then route the event into tools supported by Zapier—for example, a task system, spreadsheet, calendar, or communications workflow.

Note

Access to the FaciliPulse Zapier app may be provided as an invite or private integration while distribution is being finalized. If FaciliPulse does not appear in your Zapier account, contact support before building the Zap.

Create the connection key

1. Sign in as an organization super administrator.
2. Open Integrations and find Organization API Key in the Zapier section.
3. Select the control to generate a key.
4. Copy the new key immediately and store it in a password manager. FaciliPulse stores a hash and will not display the full value again.
5. In Zapier, add or select the FaciliPulse connection and paste the key when prompted.

The key begins with fs_live_. Zapier sends it in a request header; it should never be placed in a URL or query string.

Build and test a Zap

1. Create a Zap and select the FaciliPulse status-update trigger.
2. Choose the FaciliPulse connection you created.
3. Test the trigger. FaciliPulse returns up to three recent status events; when no event exists yet, it returns realistic sample data so fields can still be mapped.
4. Add the destination action and map only the fields it needs.
5. Test the action using a non-production destination.
6. Publish the Zap, then make one labeled facility status update and confirm the complete path.

Useful trigger fields include:

Field	Meaning
id / eventId	Stable event identifier for deduplication
orgId, orgName	Source organization
scope, scopeLabel	Facility or affected area
action, status	Applied change and resulting status
headline, statusMessage, note	Human-readable content
scheduledStart, scheduledEnd	Effective window, when present
untilFurtherNotice	Whether the update has no planned end
timestamp	Event creation time

Use eventId as a deduplication key when the destination supports one. Avoid branching solely on human-readable message text; status, scope, and action are safer mapping fields.

Manage active subscriptions

When a Zap is turned on, Zapier registers a private delivery URL with FaciliPulse. Active Zapier subscriptions appear in the Integrations workspace. Turning off or deleting the Zap should unsubscribe it. You can also remove a stale subscription from FaciliPulse.

FaciliPulse retries transient delivery failures. Rate-limited deliveries respect Zapier’s retry guidance when available. A subscription can be deactivated after repeated failures, and a destination returning 410 Gone is removed.

Rotate or revoke a key

Generating a new key replaces the existing one. Connections using the old key stop authenticating and must be updated. Revoking the key also removes active Zapier subscriptions and attempts to pause the associated Zaps.

Rotate the key when an administrator leaves, a credential is shared accidentally, or a third-party account may be compromised.

Troubleshooting

Zapier says the credentials are invalid: generate a fresh key, copy it without surrounding spaces, and update the FaciliPulse connection in Zapier.

The trigger test has sample rather than recent data: publish one test status update, wait briefly, and retest. You can still build field mappings from the supplied sample.

A published Zap stops receiving events: confirm the Zap is on, the key is still active, and its webhook subscription appears in FaciliPulse. Reconnect the Zap after a key rotation.

The Zap runs more than once: deduplicate downstream using eventId. A reliable workflow must tolerate a repeated delivery.