BriefGate for Zapier

The BriefGate Zapier integration connects client intake to the apps you already run on Zapier — start an intake when a deal closes in your CRM, send the finished files to Google Drive, post in Slack when a client opens their portal.

It is a private beta: the integration is not listed in Zapier's app directory yet. Anyone can use it today through the invite link below; it becomes public once it passes Zapier's review.

Join the BriefGate Zapier beta →


Connecting your account

  1. Open the invite link above while signed in to Zapier and accept the invitation. BriefGate then shows up in the app picker of the Zap editor.
  2. In the BriefGate dashboard, open API Keys and create a key.
    • Actions and searches need the intakes:read and intakes:write scopes.
    • The triggers need the admin scope, because a trigger registers a webhook on your account. See API key scopes.
    • A bg_test_… key never emails or texts a real client, so it is the safest choice while you build a Zap. Switch to a bg_live_… key when the Zap goes live.
  3. In Zapier, add a BriefGate step, choose Sign in, and paste the key.

Triggers

All four triggers are instant: turning the Zap on registers a webhook on your BriefGate account, and turning it off removes it again. Every delivery is checked against BriefGate's X-BriefGate-Signature header before the Zap runs. Payloads are described in webhooks.

Trigger Fires when
Intake Completed Every required item on an intake has been submitted.
Item Submitted The client submits or fills in one item.
Client Viewed Portal The client opens their portal for the first time. Refreshing the page does not fire it again.
Intake Overdue The due date passes with required items still outstanding. Fires once per intake.

Actions

Action What it does
Create Intake Starts a new intake and emails the client their portal link. Set Send Immediately to false to keep it as a draft.
Send Reminder Sends a chase message outside the automatic schedule, by email or SMS (SMS needs the SMS feature and credit). Limited to one manual reminder per intake per hour; fails with "Nothing to chase" when the intake is already completed.

Searches

Search What it returns
Find Intake One intake by ID: status, due date, progress, item statuses and chase history.
Get Intake Results Typed values for approved items (optionally also submitted ones), signed file URLs, and the list of items still missing.

Secrets are never returned to Zapier. Zapier keeps every step's output in your Zap history, and a secret item (a password or API key the client entered) can be revealed only once. Get Intake Results therefore always sends exclude_secrets=true: secret items are left out without being revealed, and you read them in the BriefGate dashboard instead.


Example Zaps

Deal won → intake sent. Your CRM's "deal won" trigger → BriefGate: Create Intake with the items you always ask for at kickoff. The client gets the portal link by email right away.

Completed intake → files in Drive. BriefGate: Intake CompletedBriefGate: Get Intake Results → a Google Drive step that uploads each file from its signed URL into the client's project folder.

Client opened the portal → heads-up in Slack. BriefGate: Client Viewed Portal → a Slack message to the project channel, so you know the request reached the client.

Overdue intake → one more nudge. BriefGate: Intake OverdueBriefGate: Send Reminder, so the client hears from you the moment the deadline slips.


Resources