Per-pair page

Connect GCP Cloud Functions to Notion in two minutes.

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

Connect GCP Cloud Functions and Notion See reverse direction

Trigger app

GCP Cloud Functions as the trigger

Workflows fire when something happens in GCP Cloud Functions.

GCP Cloud Functions has no triggers yet. Use the catalog's universal Webhook trigger as the upstream.

Action app

Notion as the action

Workflows do something in Notion, instantly.

See all 12 actions →

Both directions

Pick the way that fits your stack.

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

GCP Cloud Functions → Notion

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

0 GCP Cloud Functions triggers wired to 12 Notion actions.

Notion → GCP Cloud Functions

Or fire it the other way around.

3 Notion triggers wired to 2 GCP Cloud Functions actions downstream.

See Notion → GCP Cloud Functions →

How it works

Connect GCP Cloud Functions and Notion in five steps.

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

1
Connect
Authorize GCP Cloud Functions and Notion
Open Tiny Command, authorize GCP Cloud Functions and Notion once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a GCP Cloud Functions trigger
Drop the GCP Cloud Functions → New event trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/gcp-cloud-functions.event
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
Action
Add the Notion action
Drop the Notion → Append Content action below it. Map fields from the GCP Cloud Functions payload into the Notion inputs.
notion.append-blocks
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 GCP Cloud Functions + Notion.

How long does it take to connect GCP Cloud Functions and Notion on Tiny Command?

Under two minutes. Authorize GCP Cloud Functions and Notion once each, drop the GCP Cloud Functions trigger and Notion action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.

Is the GCP Cloud Functions ↔ Notion integration real-time?

Yes. Both GCP Cloud Functions and Notion 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 GCP Cloud Functions and Notion?

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 Notion.

What GCP Cloud Functions events can trigger a Notion workflow?

Use Tiny Command's universal Webhook trigger to receive GCP Cloud Functions events, then run any of the 12 Notion actions downstream.

Do I need a paid plan to use GCP Cloud Functions with Notion?

No. There's a free tier that covers most GCP Cloud Functions+Notion use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.

What if I want Notion → GCP Cloud Functions instead?

Build it the same way, in reverse. There's a dedicated /integrations/notion/with/gcp-cloud-functions page with the reverse-direction triggers and actions.