Use real triggers and actions
The native connectors include Status Changed, Set Status, and Return to Automatic—not just a generic webhook payload.
IFTTT LIVE · ZAPIER PRIVATE BETA
IFTTT live · Zapier private betaDocumentation reviewed September 10, 2026
Let your final status trigger what happens next.
Presence is now publicly available on IFTTT with native OAuth, a Status Changed trigger, and status actions. Presence for Zapier remains an installable private beta, and supported webhook workflows remain available.
TKTim KellerTeam memberIn a MeetingAvailable 2:30 PM your time
MSMaya SinghTeam memberAvailableCome on in
JCJordan ChenTeam memberOn a CallCheck back shortly
ARAlex RiveraTeam memberFocusAvailable 3:15 PM your time
BUILT FOR FLEXIBLE WORKPLACE AND SMART-HOME AUTOMATIONS
One clear answer before someone interrupts.
Presence combines only the availability connections you approve into one simple, privacy-safe status. The people around you see whether now is a good time—not the private details behind the answer.
Wait for the final answer
The automation runs only after Presence resolves calendars, live meetings, calls, Focus, Away, custom statuses, and manual choices.
Share a deliberately small payload
Presence sends the simplified status, display message, color, and event time—not calendar titles, attendees, callers, or conversation content.
Keep Presence dependable
Duplicate updates are skipped. A slow, broken, or disconnected automation cannot block status calculation or other Presence outputs.
SET IT UP ONCE
Presence works quietly in the background.
- 1Connect Presence on IFTTT
Open the public Presence service on IFTTT, connect your Presence account through secure OAuth, and choose the Applet or Connection you want to use.
- 2Join the Zapier beta
Use the private-beta invitation in your Presence dashboard, accept Presence in Zapier, then connect your account through the secure OAuth screen.
- 3Choose a native workflow
Start with Presence Status Changed, Set a Presence Status, or Return Presence to Automatic. No webhook URL is required for the native Zapier beta.
- 4Keep webhooks when useful
Zapier Catch Hooks and IFTTT Webhooks remain supported. Paste the private URL in Dashboard → Connections → Zapier & IFTTT and send the built-in test.
PRIVACY FIRST
Availability is shared. Calendar details are not.
Meeting titles, attendees, call participants, precise coordinates, chat, recordings, audio, and video stay out of shared views. Every user controls their own connections and links.
COMMON QUESTIONS
What people want to know.
Is Presence listed in the Zapier or IFTTT app directory?
Presence is publicly listed on IFTTT at ifttt.com/presence. Presence for Zapier is available as an installable private beta but is not yet a public Zapier directory listing. A public listing identifies availability and compatibility; it does not imply sponsorship or endorsement.
What does Zapier receive?
A JSON event containing event, status, message, color, and occurredAt. IFTTT receives the same fields plus value1, value2, and value3 for its standard Webhooks action mapping.
Are webhook URLs private?
Yes. They act like credentials, are encrypted at rest, are never displayed again after setup, and should be replaced if shared accidentally. Native connections instead use revocable OAuth access tokens.
Can developers review the API boundary?
Yes. Presence publishes production Automation API documentation describing authentication, triggers, actions, errors, and the data it deliberately excludes.
GET STARTED
Make availability clear.
Try Presence free during the beta using your existing tablet or browser.
Start free