Integrations

Overview

Integrations connect Teamtastic to tools you already use. Most configuration lives under Settings → Integrations and requires a Director or Manager role. Personal meeting links are set per user in Profile.

Some integrations are gated by plan. Plan tier is noted in each section heading.

Zoom and Google Meet links

Each user can save a personal Zoom or Google Meet room URL on their Profile. Directors may also set an org-wide default room. When scheduling a call, the saved link is attached to the call entry and shown on Today. Available on all plans.

This is a stored link, not an OAuth connection. Teamtastic does not host the meeting or create calendar events for you. Paste the URL once and it is reused for future calls.

Inbound email-to-task (Team plan)

Forward email to a workspace-specific alias to auto-create tasks.

Director configures the alias and routing under Integrations.
Use a dedicated address (for example tasks@yourcompany.teamtastic.net): avoid personal inboxes.
Subject line becomes the task title; body becomes the description.
Attachments on the forwarded email become task attachments (up to your plan's per-file limit).
Optional routing rules can assign the task to a specific team or project based on the sender or subject pattern.

Outgoing webhooks (Business plan)

Send signed task and PTO events to any HTTPS endpoint for custom dashboards, automation platforms, or internal tools.

Set the outbound webhook URL in Integrations.
Teamtastic signs payloads with HMAC-SHA256; verify signatures on your server.
Automation rules (Managers and Directors) can also call webhooks on task or PTO events.
Retries with exponential backoff for non-2xx responses, with delivery history in the integrations panel.

Incoming webhooks (Business plan)

Receive events from external systems and post them as formatted messages into a Teamtastic channel. Teamtastic automatically recognises payloads from popular providers and formats them into readable summaries.

Supported providers

GitHub — pull request opened/closed/merged, push events, issue comments, CI status. Example: "PR #142 merged — fix login timeout · opened by alex".
Sentry — new issue alerts, error spikes, and resolved events. Example: "New error · TypeError: Cannot read properties of undefined · 14 occurrences".
Railway — deploy succeeded, deploy failed, and service health events. Example: "Deploy succeeded · main · teamtastic-prod · 43s".
Generic JSON — any system that POSTs JSON. Teamtastic posts the raw payload summary to the channel with field highlighting.

Setup

Director generates a webhook URL and optional shared secret in Settings → Webhooks.
Paste the URL into the external service's webhook settings (GitHub repo → Settings → Webhooks, Sentry project → Settings → Integrations, etc.).
Choose which channel should receive the formatted messages.
Incoming events appear as bot messages in that channel with a provider badge and formatted summary.

Provider detection

Teamtastic detects the provider automatically from the request headers (X-GitHub-Event, X-Sentry-Hook-Resource, etc.) — no manual configuration needed per event type. Unknown providers fall back to a generic formatted card.

Sign-in with Google

Workspaces can let members sign in with their Google account as an authentication method. This is separate from any meeting or calendar feature. Use the same work account consistently if you mix password and Google sign-in.

Security notes

Rotate webhook secrets if leaked — generate a new URL in Settings → Webhooks.
Do not paste webhook URLs in public tickets or commit them to public repos.
Inbound email aliases should be treated as creation endpoints; restrict who can send mail to them.
Outgoing webhook payloads are signed with HMAC-SHA256; always verify the signature before trusting the payload.

Troubleshooting

See Troubleshooting for webhook delivery failures and inbound email routing issues.