Per-pair page

Connect Gmail to Kit (ConvertKit) in two minutes.

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

Connect Gmail and Kit (ConvertKit)See reverse direction

Trigger app

Gmail as the trigger

Workflows fire when something happens in Gmail.

New EmailWebhook

Action app

Kit (ConvertKit) as the action

Workflows do something in Kit (ConvertKit), instantly.

Both directions

Pick the way that fits your stack.

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

Gmail → Kit (ConvertKit)

When something happens in Gmail, do it in Kit (ConvertKit).

1 Gmail triggers wired to 4 Kit (ConvertKit) actions. Most-used pairing: New Email → Add Subscriber.

New Email

Kit (ConvertKit) → Gmail

Or fire it the other way around.

3 Kit (ConvertKit) triggers wired to 27 Gmail actions downstream.

See Kit (ConvertKit) → Gmail →

How it works

Connect Gmail and Kit (ConvertKit) in five steps.

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

1
Connect
Authorize Gmail and Kit (ConvertKit)
Open Tiny Command, authorize Gmail and Kit (ConvertKit) 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 Kit (ConvertKit) action
Drop the Kit (ConvertKit) → Add Subscriber action below it. Map fields from the Gmail payload into the Kit (ConvertKit) inputs.
convertkit.add-subscriber
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 + Kit (ConvertKit).

How long does it take to connect Gmail and Kit (ConvertKit) on Tiny Command?

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

Is the Gmail ↔ Kit (ConvertKit) integration real-time?

Yes. Both Gmail and Kit (ConvertKit) 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 Kit (ConvertKit)?

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 Kit (ConvertKit).

What Gmail events can trigger a Kit (ConvertKit) 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 Kit (ConvertKit)?

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

What if I want Kit (ConvertKit) → Gmail instead?

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