Per-pair page

Connect Gmail to GitBook in two minutes.

Real-time triggers from Gmail, ready-made actions in GitBook. Filter, transform, and route without writing a line of code.

Connect Gmail and GitBook See reverse direction

Trigger app

Gmail as the trigger

Workflows fire when something happens in Gmail.

New EmailWebhook

Action app

GitBook as the action

Workflows do something in GitBook, instantly.

Both directions

Pick the way that fits your stack.

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

Gmail → GitBook

When something happens in Gmail, do it in GitBook.

1 Gmail triggers wired to 3 GitBook actions. Most-used pairing: New Email → Get GitBook Space Content.

New Email

GitBook → Gmail

Or fire it the other way around.

0 GitBook triggers wired to 27 Gmail actions downstream.

Use any trigger in the catalog as the upstream.

See GitBook → Gmail →

How it works

Connect Gmail and GitBook in five steps.

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

1
Connect
Authorize Gmail and GitBook
Open Tiny Command, authorize Gmail and GitBook once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Gmail trigger
Drop the Gmail → New Email trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/google-gmail.trigger-email-received
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 GitBook action
Drop the GitBook → Get GitBook Space Content action below it. Map fields from the Gmail payload into the GitBook inputs.
gitbook.get-space-content
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 Gmail + GitBook.

How long does it take to connect Gmail and GitBook on Tiny Command?

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

Is the Gmail ↔ GitBook integration real-time?

Yes. Both Gmail and GitBook 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 Gmail and GitBook?

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

What Gmail events can trigger a GitBook workflow?

Any of the 1 Gmail triggers, including "New Email". Each fires in real time when the matching event happens in Gmail.

Do I need a paid plan to use Gmail with GitBook?

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

What if I want GitBook → Gmail instead?

Build it the same way, in reverse. There's a dedicated /integrations/gitbook/with/google-gmail page with the reverse-direction triggers and actions.