> ## Documentation Index > Fetch the complete documentation index at: https://docs.thefaithapp.com/llms.txt > Use this file to discover all available pages before exploring further. # Connect calendars and church automations > Connect Google or Outlook schedules and use Zapier or Make through invitation access. Calendar and automation features are live. **Zapier is available by invitation** and remains private; its public listing is deferred. **Make is also available by invitation**, with public directory review pending. You can use both integrations now through their invitations. Connected calendars add Google and Outlook authorization, calendar choice, schedule updates, cancellations, and sync history alongside existing private calendar subscriptions. Church teams manage shared calendars from Events; members manage their personal schedule from the Volunteer Hub. Registered events stay in members' calendars even when an early morning or late evening event falls on a different date in UTC. Calendar connections can now finish authorization and load available calendars reliably. If a connection stopped after sign-in, choose **Check authorization** to continue without signing in again. Members who opt into serving sync can receive real calendar invitations from their church's connected organizer account. Declining those invitations updates their serving response. Personal appointment copies provide a TheFaithApp response link when organizer invitations are unavailable. Serving response links now open a member page with the role, date, time, timezone, and location. Members can accept or decline without a staff account; declining requires a reason shared with their serving leader. Opening a link does not record a response. Existing links keep their original expiry, and unavailable invitations show guidance to the member's schedule or serving leader. **Platform > Developers** adds scoped automation keys, supported triggers and actions, and recent workflow outcomes for Zapier and Make. Keys can expire or be revoked. Repeated actions reuse their recorded outcome so a provider retry does not repeat the same work. Automation connections accept only TheFaithApp's service addresses, so a mistyped destination cannot receive your automation key. Creating an automation key now honors the expiration shown in the form. The date remains in place if a request fails, so retrying preserves the intended expiry. Creating a new person through Zapier or Make now succeeds reliably. Updating someone already in the church keeps their original source, and matching email addresses continue to reuse the existing person. Custom connector setup now shows the correct way to authenticate an automation key. **Return Success** gives Zapier and Make workflows a final test action that does not change church records. Current versions check that the connected account is still authorized; older private Zapier versions return success locally. The current Zapier invitation version uses the live church connection and clearer person, donation, date, and registration fields. Trigger setup samples match the fields delivered when the workflow runs. Background retry timing has been corrected to give long-running work time to finish before it is attempted again. Mobile version **4.0.17** is prepared for release validation with the member calendar connection flow. Make's advanced **Make an API call** option supports authenticated requests for workflows that need additional API operations. Its connection uses your live church, so action tests can change records or send messages. Use suitable test records, or choose **Return Success** to check the connection without changing church records. Public directory approval remains pending. Open **Platform > Developers > Set up Zapier** or **Set up Make** to access the invitation. If an invitation is unavailable, contact [support@thefaithapp.com](mailto:support@thefaithapp.com) with your church name and preferred provider. Review uncertain message deliveries before trying again. Read [Events and Volunteers](/product/events-and-volunteers) and [Platform, Access and Integrations](/product/platform-access-integrations) for setup and troubleshooting. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.