Skip to content
Per-pair page

Connect Slack to GCP Cloud Functions in two minutes.

Real-time triggers from Slack, ready-made actions in GCP Cloud Functions. Filter, transform, and route without writing a line of code.

Trigger app
Slack as the trigger

Workflows fire when something happens in Slack.

See all 13 triggers →
Action app
GCP Cloud Functions as the action

Workflows do something in GCP Cloud Functions, instantly.

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

SlackGCP Cloud Functions

When something happens in Slack, do it in GCP Cloud Functions.

13 Slack triggers wired to 2 GCP Cloud Functions actions. Most-used pairing: App Home OpenedCall Cloud Function.

GCP Cloud FunctionsSlack

Or fire it the other way around.

0 GCP Cloud Functions triggers wired to 45 Slack actions downstream.

  • Use any trigger in the catalog as the upstream.
See GCP Cloud FunctionsSlack
Popular pairings

Common Slack → GCP Cloud Functions workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 6 of 26 combinations
How it works

Connect Slack and GCP Cloud Functions in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize Slack and GCP Cloud Functions

    Open Tiny Command, authorize Slack and GCP Cloud Functions once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Slack trigger

    Drop the Slack → App Home Opened trigger onto the canvas. Tiny Command auto-registers the webhook.

    POST /v1/webhooks/slack.trigger-app-home-opened
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the GCP Cloud Functions action

    Drop the GCP Cloud Functions → Call Cloud Function action below it. Map fields from the Slack payload into the GCP Cloud Functions inputs.

    gcp-cloud-functions.call-function
  5. 5
    Publish
    Publish and forget

    Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Slack + GCP Cloud Functions.

How long does it take to connect Slack and GCP Cloud Functions on Tiny Command?
Under two minutes. Authorize Slack and GCP Cloud Functions once each, drop the Slack trigger and GCP Cloud Functions action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Slack ↔ GCP Cloud Functions integration real-time?
Yes. Both Slack and GCP Cloud Functions expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.
Can I filter or transform data between Slack and GCP Cloud Functions?
Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit GCP Cloud Functions.
What Slack events can trigger a GCP Cloud Functions workflow?
Any of the 13 Slack triggers, including "App Home Opened". Each fires in real time when the matching event happens in Slack.
Do I need a paid plan to use Slack with GCP Cloud Functions?
No. There's a free tier that covers most Slack+GCP Cloud Functions use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.
What if I want GCP Cloud Functions → Slack instead?
Build it the same way, in reverse. There's a dedicated /integrations/gcp-cloud-functions/with/slack page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Slack.


Wire Slack to GCP Cloud Functions in 2 minutes.

Free tier available. No credit card. No onboarding call.