We use cookies for essential site functions and anonymous analytics. Choose what to allow.
Kumar Makala · Founder & CEO, SyncRivo
Kumar Makala leads platform engineering and technical content at SyncRivo, focused on enterprise messaging interoperability, messaging bridge architecture, and cross-platform integration patterns across Slack, Microsoft Teams, Google Chat, Zoom Team Chat, and Cisco Webex. LinkedIn
Updated · 9 min read
Terraform Cloud's own notifications post run completions, apply failures, drift detection events, and Sentinel policy failures. SyncRivo bridges the human discussion about them between Slack, Teams, Webex, Google Chat, and Zoom.
SyncRivo does not relay Terraform Cloud notifications — messages posted by bots and apps are not bridged. Terraform Cloud's own notifications post the alerts; SyncRivo lets engineers on Slack and stakeholders on Teams work the issue in one bridged channel.
Terraform Cloud's own notifications post these events. SyncRivo bridges the human conversation about them across Slack, Teams, Webex, Google Chat, and Zoom.
Successful infrastructure apply events — new resources provisioned, configuration changes applied — posted by Terraform Cloud's own notifications. SyncRivo bridges the human follow-up discussion between Slack and Teams.
Plan or apply failure events posted by Terraform Cloud's own notifications — while SyncRivo bridges the response conversation so Slack and Teams users coordinate in one channel.
Plan-complete events awaiting manual confirmation before apply, posted by Terraform Cloud's own notifications. Reviewers on either platform can discuss the pending apply in a bridged channel.
Infrastructure drift detection events — real infrastructure diverged from Terraform state — posted by Terraform Cloud's own notifications, with the investigation discussed across Slack and Teams in a bridged channel.
Sentinel policy check failures (soft-fail or hard-fail) posted by Terraform Cloud's own notifications. The infrastructure team and the compliance owner can discuss overrides across platforms in a bridged channel.
Terraform Cloud workspace health assessment failures posted by Terraform Cloud's own notifications, with the remediation conversation bridged between Slack and Teams.
In Terraform Cloud, go to any workspace → Settings → Notifications → Create a Notification. Select Slack as the destination and choose triggers: run:completed, run:errored, run:needs_attention, assessment:drifted, assessment:failed, policy_check:soft_failed. Terraform Cloud's built-in Slack notification includes run links, workspace context, and status icons.
Create a notification for Teams using a destination Terraform Cloud supports, or a generic webhook to a Teams-side receiver you manage. Organization-level notification configurations (Business plans) can apply to all workspaces.
Connect your Slack workspace and Microsoft Teams tenant to SyncRivo. Your Slack and Microsoft admins must approve the apps.
Bridge the Slack and Teams channels where infrastructure, compliance, and leadership discuss these events. SyncRivo does not relay bot or app notifications — post a human reply in Slack and confirm it appears in the bridged Teams channel.
Example of where Terraform Cloud's own notifications might post each event. SyncRivo does not relay these notifications — it bridges the human discussion between the Slack and Teams channels.
| Terraform Cloud Event | Slack Destination | Teams Destination | Rationale |
|---|---|---|---|
| Run errored (production) | #on-call (immediate response) | Infrastructure Engineering channel | On-call investigates; leadership tracks production incidents |
| Apply completed (production) | #infrastructure (deploy log) | Engineering Leads channel | Engineers track deploys; leads confirm production changes |
| Needs attention (plan awaiting approval) | #infrastructure (reviewer alert) | Engineering Leads channel | Engineers see pending applies; leads aware of blocked deploys |
| Drift detected | #infrastructure (remediation) | Compliance channel | Infra team remediates; compliance tracks state violations |
| Sentinel policy soft-failed | #infrastructure (review needed) | Compliance channel | Infra decides override; compliance monitors policy exceptions |
| Run errored (staging) | #infrastructure (Slack only) | — (no Teams notification configured) | Staging failures are dev-team scope; no leadership escalation |
| Capability | Terraform Cloud Native | SyncRivo |
|---|---|---|
| Notify Slack | ✓ Built-in Slack notification (Workspace Settings → Notifications → Slack) | ✗ Not relayed (use native notification) |
| Notify Microsoft Teams | Check HashiCorp's current destinations or use a generic webhook | ✗ Not relayed (bot/app messages are not bridged) |
| Notify Webex / Google Chat / Zoom | Generic webhook | ✗ Not relayed |
| Human discussion between Slack and Teams users | ✗ Not available | ✓ Bridged human conversation |
| Threads, @mentions, and files in the incident discussion | ✗ Not available | ✓ Synced across bridged channels |
| M&A: engineers on both organizations' platforms discuss infrastructure changes | ✗ Not available | ✓ Bridged human conversation across Slack, Teams, Google Chat, Webex, and Zoom |
Terraform Cloud (now HCP Terraform) has a built-in Slack workspace notification integration (Workspace Settings → Notifications → Slack) that routes run plan results, apply completions, apply failures, and policy check events to a Slack channel. For Teams, check HashiCorp's current notification destinations or use Terraform Cloud generic webhooks (Workspace Settings → Notifications → Webhook) with a Teams-side receiver you manage. SyncRivo does not relay Terraform Cloud notifications — messages posted by bots and apps are not bridged. Terraform Cloud's own notification integrations post the run events; SyncRivo bridges the human discussion between chat platforms, so people on Slack and Teams can work the issue in one bridged channel.
In Terraform Cloud, go to the workspace → Settings → Notifications → Create a Notification, choose a destination Terraform Cloud supports for Teams (or a generic webhook to a Teams-side receiver you manage), and select the triggers: run completed, run needs attention, run errored, drift detected. SyncRivo does not relay Terraform Cloud notifications — messages posted by bots and apps are not bridged. Terraform Cloud's own notification integrations post the run events; SyncRivo bridges the human discussion between chat platforms, so people on Slack and Teams can work the issue in one bridged channel.
None. SyncRivo does not relay Terraform Cloud notifications — messages posted by bots and apps are not bridged. Terraform Cloud's own notification integrations post the run events; SyncRivo bridges the human discussion between chat platforms, so people on Slack and Teams can work the issue in one bridged channel. Terraform Cloud notification triggers include run:planning, run:needs_attention, run:applying, run:completed, run:errored, assessment:drifted, assessment:failed, and policy_check:soft_failed — configure them in Terraform Cloud's own notification settings for each channel.
Yes. Terraform Cloud continuous validation (available on Plus and Enterprise plans) runs health assessments on managed workspaces and detects configuration drift — when real infrastructure diverges from the Terraform state. When drift is detected, Terraform Cloud fires an assessment:drifted notification to the destinations configured in Terraform Cloud. SyncRivo does not relay that notification, but it can bridge the channel where your infrastructure and compliance teams discuss the drift, so people on Slack and Teams investigate together.
No — SyncRivo does not relay bot or app notifications. Post-merger organizations often have infrastructure teams on different platforms — one organization's platform engineers on Slack, the other on Teams. Terraform Cloud's own notification integrations post run events to each team's channels; SyncRivo bridges the human conversation between Slack and Teams so the full cross-platform team can coordinate on infrastructure changes without platform migration.
Yes. Terraform Cloud Sentinel policy checks fire notifications when a run's policy evaluation completes. A policy_check:soft_failed notification indicates a policy failed but can be overridden; policy_check:hard_failed blocks the apply. Configure these in Terraform Cloud's notification settings. SyncRivo does not relay the notifications themselves, but it can bridge the discussion between the infrastructure team on Slack and the compliance owner on Teams.
Bridge the human discussion about infrastructure changes across any combination of Slack, Teams, Google Chat, Webex, and Zoom Team Chat.
Slack + Teams + Google Chat
Bridge Slack, Teams, and Google Chat simultaneously.
Slack + Teams + Webex
Connect Slack and Teams users with Cisco Webex.
Slack + Teams + Zoom
Unify Slack, Teams, and Zoom Team Chat.
Slack + Google Chat + Zoom
Three-way bridge for Slack, Google Chat, and Zoom.
Slack + Google Chat + Webex
Unify Slack, Google Chat, and Cisco Webex.
Slack + Zoom + Webex
Bridge Slack with both Zoom and Webex.
Teams + Google Chat + Zoom
Connect Teams, Google Chat, and Zoom Team Chat.
Teams + Google Chat + Webex
Bridge Teams, Google Chat, and Cisco Webex.
Teams + Zoom + Webex
Unify Teams, Zoom, and Webex in one bridge.
Google Chat + Zoom + Webex
Connect Google Chat with Zoom and Webex.
Terraform Cloud's own notifications post the events. SyncRivo bridges the human conversation between Slack, Teams, Webex, Google Chat, and Zoom so the whole team can respond together.
Ready to connect? Slack ↔ Teams connection setup →