Integration options

Use the simplest integration that reliably completes the job. Most organizations can start with a no-code connection and move to the API only when they need custom behavior.

Option	Best for	Setup level	Authentication
Slack	Posting status alerts to a staff channel	No code	Slack authorization
Microsoft Teams	Posting alerts to a work channel or configured chat	No code	Microsoft authorization
Zapier	Starting workflows in other apps	Low code / no code	FaciliPulse integration key
Webhooks	Sending signed events to your own service	Developer	Scoped API key + signing secret
Website and TV views	Showing member-facing status	No code	Public organization configuration
REST API	Reading or managing data from your software	Developer	Scoped API key

Find integration settings

Sign in as an organization super administrator and open Integrations in the facility administration workspace. That area shows connection status, test controls, API credentials, active webhook destinations, and delivery history available to your organization.

Choose the event source carefully

Integrations react to real FaciliPulse events. A saved draft or a preview that explicitly suppresses delivery does not necessarily create an external event. Test the same action your staff will use in production—for example, publishing an area closure—not merely changing an unrelated setting.

Common status events include:

• facility.override_changed
• facility.status_changed
• area.status_changed
• notification.sent

Generic webhooks can also subscribe to member.prefs_updated. Event availability depends on the workflow producing it; verify the event you need during acceptance testing.

A safe rollout pattern

1. Connect a private test channel or staging endpoint.
2. Trigger one clearly labeled test update.
3. Confirm the scope, status, note, and timestamp at the destination.
4. Test recovery by temporarily returning a failure from your endpoint, if applicable.
5. Move the integration to its production destination and document who owns it.

Keep integration keys and signing secrets out of browser code, screenshots, support tickets, and shared documents. Rotate a credential immediately if it may have been exposed.