front-integrations

Front platform integrations for Sea Haven Industries. Two scheduled Lambdas:

1. SLA Monitor — checks Front conversations for SLA breaches and sends tiered Slack alerts
2. User Sync — pulls Google Workspace user profiles and syncs job title + phone to Front teammate custom fields

Architecture

EventBridge (every 15 min, 8 AM-5 PM ET, Mon-Fri)
    |
    v
front-sla-monitor (Python 3.12, arm64)
    |
    +-- Secrets Manager --> front-integrations/front-api-token
    +-- Secrets Manager --> front-integrations/slack-bot-token
    |
    +-- GET Front API /inboxes --> filter to configured inboxes
    +-- GET Front API /inboxes/{id}/conversations --> open conversations
    |
    +-- DynamoDB (front-sla-alerts) --> dedup + first-run-of-day detection
    |
    +-- Morning (first run) --> summary to #front-sla-alerts
    +-- Tier 1 (1 hr) --> Slack DM assignee or #front-sla-alerts
    +-- Tier 2 (1 day) --> Slack DM Adam


EventBridge (weekdays 6:00 AM ET)
    |
    v
front-user-sync (Python 3.12, arm64)
    |
    +-- Secrets Manager --> front-integrations/google-service-account
    +-- Secrets Manager --> front-integrations/front-api-token
    |
    +-- GET Google Admin Directory API --> list users in target OUs
    +-- PATCH Front API /teammates/alt:email:{email} --> update custom_fields

SLA Rules

Tier	Threshold	Action
1	1 business hour without reply	Slack DM the assignee, or post to #front-sla-alerts if unassigned
2	1 business day without reply	Slack DM Adam

Business time counts weekday hours only (Mon-Fri, Eastern time). Alerts are only sent during business hours (8 AM-5 PM ET). Overnight breaches produce a single morning summary.

AWS Resources

• Stack: front-integrations (SAM, us-east-1)
• Lambda: front-sla-monitor — Python 3.12, arm64, 256 MB, 300s timeout, 60-day log retention
• Lambda: front-user-sync — Python 3.12, arm64, 256 MB, 300s timeout, 60-day log retention
• DynamoDB: front-sla-alerts — alert history per conversation + monitor state, 7-day TTL
• EventBridge: SLA check every 15 min during business hours; user sync daily at 6 AM ET weekdays

Secrets (Secrets Manager)

Secret	Purpose
front-integrations/front-api-token	Front API token (shared by both Lambdas)
front-integrations/slack-bot-token	Slack Bot User OAuth Token for SLA alerts
front-integrations/google-service-account	Google Cloud service account JSON key

Setup

1. Create the Slack App

1. Go to https://api.slack.com/apps and create Front SLA Monitor (see slack-app-manifest.yaml)
2. Add Bot Token Scopes: chat:write, users:read, users:read.email
3. Install to workspace, copy Bot User OAuth Token
4. Create #front-sla-alerts channel and invite the bot

2. Create a Front API Token

1. Front > Settings > Developers > API tokens
2. Create a token with conversation read + teammate read/write scope

3. Set Up Google Workspace Service Account

1. Enable Admin SDK API in Google Cloud Console
2. Create service account front-directory-sync, create JSON key
3. Enable Domain-Wide Delegation, copy Client ID
4. In Google Workspace Admin: Security > API Controls > Domain-Wide Delegation
5. Add Client ID with scope: https://www.googleapis.com/auth/admin.directory.user.readonly

4. Create Custom Fields in Front

1. Settings > Custom Fields > Teammates tab
2. Create: Job Title (String) and Phone (String)

5. Store Secrets in AWS

aws secretsmanager create-secret \
  --name "front-integrations/front-api-token" \
  --secret-string "YOUR_FRONT_API_TOKEN" \
  --region us-east-1

aws secretsmanager create-secret \
  --name "front-integrations/slack-bot-token" \
  --secret-string "xoxb-YOUR-SLACK-BOT-TOKEN" \
  --region us-east-1

aws secretsmanager create-secret \
  --name "front-integrations/google-service-account" \
  --secret-string file://path-to-service-account-key.json \
  --region us-east-1

6. Deploy

sam build
sam deploy --guided

Or push to main to trigger the GitHub Actions deploy workflow.

7. GitHub Actions Secrets

Secret	Value
AWS_DEPLOY_ROLE_ARN	Org-wide OIDC deploy role (set after OIDC role is added)
SAM_PARAMETER_OVERRIDES	FrontApiTokenSecretArn=arn:... SlackBotTokenSecretArn=arn:... GoogleServiceAccountSecretArn=arn:... SlackAlertChannel=CXXXXXXXXXX

Manual Testing

aws lambda invoke --function-name front-sla-monitor --payload '{}' /dev/stdout --region us-east-1
aws lambda invoke --function-name front-user-sync --payload '{}' /dev/stdout --region us-east-1

Configuration

SLA Monitor

Parameter	Default	Description
AckSlaMinutes	60	Business minutes before Tier 1 alert
ActionSlaMinutes	1440	Business minutes before Tier 2 alert
AdamEmail	adam@seahavenind.com	Tier 2 escalation recipient
SlackAlertChannel	—	Channel ID for broadcast alerts
MonitorInboxes	Triage,California,...	Inbox names to monitor (empty = all shared)
SlaMonitorStartDate	2026-05-14	Date monitoring begins

User Sync

Parameter	Default	Description
GoogleAdminEmail	adam@seahavenind.com	Google Workspace admin to impersonate
GoogleOrgUnits	/Office/Scheduling,/Office/Operations	Org unit paths to sync