Integrations (Slack, Discord, PlusVibe, and webhooks)

Who this is for

Workspace admins wiring chat notifications, automation webhooks, and PlusVibe credentials. This page is not for REST clients; those use API keys instead (see API keys and programmatic access).

When to use this page

When you need to add or rotate an outbound integration: a Slack channel for audit alerts, a Discord webhook, a Zapier or Make.com automation hook, or the PlusVibe API credentials that the outbound pipeline depends on.

Before you start

• For Slack and Discord, generate the webhook URL inside the provider first and have it on the clipboard before you reach the form.
• For Zapier or Make.com, set up the Zap or scenario in the provider, copy the webhook URL it generates, and choose which audit event should fire it.
• For PlusVibe, gather the workspace ID, API key, webhook signing secret, and optional default campaign ID from the PlusVibe settings panel. See PlusVibe setup: required fields and first sync for the full first-time setup.

In the app

Open Integrations in the sidebar group of the same name. The page title is Integrations with subtitle "Connect your audit platform to external services." A status grid shows each integration as Connected or Not configured:

Card	Description
Slack	Receive audit notifications in Slack channels
Discord	Send audit results to Discord channels
Zapier / Make.com	Connect to 5000+ apps via webhook automations
PlusVibe	Lead outreach and email campaign automation

Slack

• Paste the Slack webhook URL and an optional Channel (for example #audits).
• Save rejects masked URLs containing • with Error: Please enter a new Slack webhook URL.
• Send test posts a test payload. The page shows Slack test message sent on success, or Slack test failed: <reason> on failure.

Discord

• Paste the Discord webhook URL.
• The same masked-URL guard and Send test behaviour as Slack.

Zapier and Make.com

• Add Webhook URL rows and an Event filter. Available events: All events, Audit completed, Audit failed, Score drop, Lead retargeted.
• Add webhook persists the subscription. Active subscriptions lists each row's URL, event badge, failure count, and last-triggered timestamp, with a delete (trash) action per row.

PlusVibe

Start with PlusVibe setup: required fields and first sync for the full setup and the writeback contract.

• Workspace ID is required. The form rejects an empty value with Error: Workspace ID is required.
• API key is a password field. The dashboard only sends the value on save when it changes; the masked * value returned from the server is treated as no-op.
• Webhook signing secret. Leave the placeholder •••••••••••••••• alone unless you are replacing the secret.
• Default campaign ID (optional).
• After a successful save: PlusVibe configured successfully banner, plus controls for Webhook URL, Register via API, Test API key, List workspaces, and Disconnect.

PlusVibe blocklist

The blocklist excludes specific domains or contact emails from the outbound pipeline.

• Load blocklist fetches the current entries.
• Add to blocklist accepts comma- or newline-separated values.
• Rows can be removed individually once loaded.

PlusVibe writeback merge fields

The writeback that runs after each completed audit pushes a set of variables onto the Plusvibe lead. Templates reference them with the custom_ prefix. The full list and the per-step indexed variants live in PlusVibe setup: required fields and first sync. The short version:

• Slim profile (outbound, the Plusvibe sync default). 18 audit keys (ai_citation_score, content_authority_score, ux_score, nav_clarity_score, brand_health_score, tap_target_count, image_savings_mb, sitemap_date, unanswered_questions_count, unanswered_q_count, audit_url, site_url, community_source, community_question, audit_topic, stale_pages_finding, trust_signal_finding, console_or_dev_flag) plus three body keys (email_subject, email_body, email_cta).
• Full profile (dashboard customers and warm replies). 10 keys including audit_url, audit_summary, audit_grade, top_issue, the three body keys, and three scored breakdowns (audit_seo_score, audit_perf_score, audit_security_score).
• Per-step sequences. When a campaign has an entry in tenant_integrations.config.campaignSequences, the writeback also pushes indexed variants (custom_email_subject_<n>, custom_email_body_<n>, custom_email_cta_<n>) and, for reminder_resend archetypes, the per-step custom_email_step_<n>_intro key.

If your Plusvibe templates render {{custom_x}} literally even after a writeback, the most common cause is a missing custom_ prefix on the template side; Plusvibe adds it automatically when storing variables.

Common pitfalls

• Slack or Discord test fails after a save. Regenerate a fresh webhook URL in the provider and paste the new value. Old or revoked URLs return a 4xx that the dashboard surfaces verbatim.
• PlusVibe still shows Not configured after save. Open the Connection status on PlusVibe overview and confirm Integrations actually saved (the page should show PlusVibe configured successfully).
• Webhook signing secret reset by accident. Pasting any non-placeholder value into the secret field overwrites the stored secret on save. To keep the existing one, leave the field untouched.
• Zapier or Make.com subscription stops firing. Inspect the failure count and last-triggered timestamp in Active subscriptions. A repeatedly-failing destination is silently deactivated after the failure threshold; rotate the URL and add it again to resume.

If something goes wrong

A page-wide banner at the top surfaces save and test results. Errors show Error: <getErrorMessage output>; successes show short confirmations. The Dismiss button clears the banner. The exact text in <reason> tends to point at the underlying API error (rate limit, validation, expired secret), so paste it into the issue tracker rather than re-running blind.

Related

• PlusVibe setup: required fields and first sync
• API keys and programmatic access
• PlusVibe overview
• Docs for the HTTP schemas