Integration directory

Google Forms × Slack — for agencies

The same integration, scaled to many clients. Client workspaces, per-client Slack destinations, unlimited forms and rules, flat billing. For lead-routing operations and managed-marketing agencies running 10–50 clients.

  • Client workspaces, no permission bleed
  • Unlimited forms, rules, responses
  • Flat $49/month, not per-client
Spec

The agency-shaped integration

Google FormsSlackIntegration
Trigger
New form submissionin any client's Google Form. One Apps Script trigger per form; lives in the client's Google account.
Action
Post to the client's Slack workspacevia that client's incoming webhook. Routing rules per form per client.
Fields available
All form fields per client form: fully isolated. Client A can't see Client B's field schema or logs.
Quick facts

Agency-relevant limits

Forms
Unlimited
Routing rules per form
Unlimited
Responses
Unlimited
Client workspaces
Unlimited
Teammates per workspace
Unlimited
Billing model
Flat $49/mo or $490/yr
Setup

Onboarding a new client

  1. 1
    Create the client workspace in RouteForms
    Dashboard → New workspace → name it after the client. Teammates added here have access only to this workspace.
  2. 2
    Add the client's Slack webhook
    The client creates an incoming webhook in their Slack (or you do, if they've delegated Slack admin). Paste the URL into the workspace settings.
  3. 3
    Add the client's Google Form and install the script
    Same 3-step install as a single-form setup. The Apps Script lives in the client's Google account, they can rotate it any time if they're not happy with the integration.
  4. 4
    Add routing rules per form
    Lead-by-source, lead-by-budget, lead-by-region, whatever the client's playbook is. Each rule can carry its own template so VIP leads look different from standard ones.
What makes the agency shape work

Beyond a single-tenant integration

  • Workspace isolation.A junior contractor working on Client A can't see Client B's rules, logs, or webhooks. Workspace is the permission boundary.
  • Per-workspace failure alerts. When deliveries fail for Client C, the email goes to whoever owns that workspace, not the agency firehose.
  • Client-visible delivery log.Invite the client into their workspace as a viewer; they see their own pipeline without seeing your operational details. Reduces "is it working?" check-in requests.
  • Flat pricing decouples cost from client count. Zapier per-task and per-Zap billing becomes the operating story at 5+ clients; one Agency seat covers them all.
FAQ

Frequently asked questions

What does 'client workspaces' actually do?

Each client lives in its own workspace inside RouteForms. Forms, routing rules, Slack webhooks, delivery logs are scoped to the workspace, one client's submissions can never accidentally land in another client's Slack. The team adds teammates per workspace, so a junior contractor working on one client only sees that client's pipeline. Billing rolls up to one Agency subscription regardless of how many client workspaces you run.

Can each client have their own Slack workspace?

Yes, that's the canonical setup. Each workspace inside RouteForms points at a different Slack workspace via a workspace-specific incoming webhook. Client A's submissions go to Client A's Slack; Client B's to Client B's Slack. No permission bleed; nothing for the client to install (the webhook lives in their Slack, controlled by them).

How does the integration scale across 20+ clients?

Unlimited forms, unlimited routing rules per form, unlimited responses on the Agency plan. Each form's Apps Script trigger is independent, so onboarding a new client is the same 3-minute setup as the first one. The dashboard's client switcher keeps the operational surface manageable; nothing slows down as the client list grows.

Can clients see their own delivery log?

Yes, invite the client into their workspace as a viewer. They see their own delivery log (which submissions delivered, when, with what payload) but not your routing rule logic or your other clients. The viewer role is read-only; they can't edit rules or rotate webhooks.

What if a client churns?

Archive the workspace. Forms stop submitting, the Apps Script trigger keeps running (it lives in the client's Google account, not yours), but RouteForms ignores the inbound submissions. The delivery log is retained for the plan's retention window. If they come back, un-archive, nothing to reconfigure.

Is the Agency plan billed per workspace?

No, flat $49/month (or $490/year). The whole point is decoupling client count from cost. Per-client billing on tools like Zapier becomes the operating story at 5+ clients; here it's one line item regardless.

Run the integration across every client

Agency plan: $49/month, unlimited everything. Free tier for one client to validate the flow first.