Skip to content
Per-pair page

Connect Gmail to Apify in two minutes.

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

Trigger app
Gmail as the trigger

Workflows fire when something happens in Gmail.

Action app
Apify as the action

Workflows do something in Apify, instantly.

Both directions

Pick the way that fits your stack.

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

GmailApify

When something happens in Gmail, do it in Apify.

1 Gmail triggers wired to 4 Apify actions. Most-used pairing: New EmailGet Dataset Items.

ApifyGmail

Or fire it the other way around.

0 Apify triggers wired to 27 Gmail actions downstream.

  • Use any trigger in the catalog as the upstream.
See ApifyGmail
Popular pairings

Common Gmail → Apify workflows.

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

Showing 4 of 4 combinations
How it works

Connect Gmail and Apify in five steps.

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

  1. 1
    Connect
    Authorize Gmail and Apify

    Open Tiny Command, authorize Gmail and Apify once each. Both connections are available to every workflow on your account.

  2. 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. 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 Apify action

    Drop the Apify → Get Dataset Items action below it. Map fields from the Gmail payload into the Apify inputs.

    apify.get-dataset-items
  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 Gmail + Apify.

How long does it take to connect Gmail and Apify on Tiny Command?
Under two minutes. Authorize Gmail and Apify once each, drop the Gmail trigger and Apify action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Gmail ↔ Apify integration real-time?
Yes. Both Gmail and Apify 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 Apify?
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 Apify.
What Gmail events can trigger a Apify 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 Apify?
No. There's a free tier that covers most Gmail+Apify use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.
What if I want Apify → Gmail instead?
Build it the same way, in reverse. There's a dedicated /integrations/apify/with/google-gmail page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Gmail.


Wire Gmail to Apify in 2 minutes.

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