> ## Documentation Index
> Fetch the complete documentation index at: https://help.rekkeh.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set Up Integrations in Rekkeh

> Connect Rekkeh to Slack, Microsoft Teams, Google Calendar, and outbound webhooks to receive alerts, sync events, and automate notifications.

Rekkeh supports integrations with Slack, Microsoft Teams, Google Calendar, and outbound webhooks. These connections let you send alerts, sync events, and push visitor and security data into the tools your team already uses.

<Note>
  Only estate managers and super admins can configure integrations.
</Note>

## Supported Integrations

<CardGroup cols={2}>
  <Card title="Slack" icon="slack" href="#slack">
    Receive alerts and choose event types for real-time channel notifications.
  </Card>

  <Card title="Microsoft Teams" icon="teams" href="#teams">
    Send notifications to a Teams channel using an incoming webhook.
  </Card>

  <Card title="Google Calendar" icon="calendar" href="#google-calendar">
    Sync visitor and event data to a destination calendar.
  </Card>

  <Card title="Outbound Webhook" icon="webhook" href="#outbound-webhook">
    Push event data to an external system via HTTP.
  </Card>
</CardGroup>

## Slack

<Tabs>
  <Tab title="Connect">
    Click **Connect Slack** in the Rekkeh integrations page. You will be redirected to Slack OAuth to authorize Rekkeh. Choose the Slack workspace you want to connect.
  </Tab>

  <Tab title="Choose channel">
    After authorization, select the default channel where Rekkeh will post notifications. You can change this later.
  </Tab>

  <Tab title="Choose events">
    Select which events Rekkeh should send to Slack. Event groups include visitor check-ins, invalid pass attempts, incidents, and emergencies. You can also enable the **high-severity defaults** option to automatically include critical alerts.
  </Tab>

  <Tab title="Noise controls">
    Reduce notification volume with these controls:

    * **Quiet hours**: pause notifications during scheduled hours
    * **Medium severity filter**: exclude lower-priority alerts
    * **Rate limit**: cap the number of messages sent per hour
    * **Allow visitor names**: include or redact visitor names in Slack messages for privacy
  </Tab>
</Tabs>

## Teams

<Tabs>
  <Tab title="Create webhook in Teams">
    In Microsoft Teams, go to the channel where you want notifications. Open the channel menu, choose **Connectors**, and add an **Incoming Webhook**. Copy the webhook URL that Teams generates.
  </Tab>

  <Tab title="Connect in Rekkeh">
    In Rekkeh, go to **Integrations** > **Microsoft Teams**. Paste the webhook URL into the connection field. Click **Test connection** to verify Rekkeh can reach your Teams channel.
  </Tab>
</Tabs>

## Google Calendar

<Tabs>
  <Tab title="Connect">
    In Rekkeh, click **Connect Google Calendar**. You will be prompted to authorize Rekkeh via Google OAuth. Grant calendar access to the Google account that owns or manages the destination calendar.
  </Tab>

  <Tab title="Select calendar">
    After authorization, choose the destination calendar where Rekkeh will sync events.
  </Tab>

  <Tab title="Enable events">
    Turn on the recommended event types you want to sync. Typical options include scheduled visitor invites, recurring access windows, and event-based passes.
  </Tab>

  <Tab title="What syncs">
    Rekkeh syncs event titles, dates, times, and associated gate or visitor details to the selected calendar. Changes made in Rekkeh are reflected in Google Calendar automatically.
  </Tab>
</Tabs>

## Outbound Webhook

<Tabs>
  <Tab title="Coming soon in UI">
    The outbound webhook integration UI in Rekkeh is labeled **Coming soon**. You cannot configure it fully through the dashboard yet.
  </Tab>

  <Tab title="Setup via API">
    Until the UI is available, you can set up outbound webhooks through the Rekkeh API:

    1. Create a **connection** that defines the target URL and authentication headers
    2. Create a **subscription** that chooses which event types to forward
    3. **Test** the connection by triggering a sample event and verifying delivery
  </Tab>
</Tabs>