Calendar & SchedulingReal-timeUpdated June 2026

Drip integration

Ecommerce-focused subscriber events from Drip

Drip is the ecommerce-focused email automation platform, the alternative to Klaviyo for stores that want similar event-driven messaging at a different price point and feature mix. Seven actions cover the operational subscriber and event surface: Create Subscriber, Find Subscriber by Email, Apply Tag, Tag Subscriber, Remove Tag, Track Event (the lever that fires Drip campaigns), Record Event. No native triggers today (Drip's outbound webhook system is configurable per-event in their UI; native triggers ship in the next release). The integration uses a Drip account ID + API token from your account settings. Most Drip workflow logic resolves to "tag this subscriber" or "track this event", those are the two primitives Drip's campaign engine listens for. Common patterns: a Shopify Order Created tracks a "purchase" event in Drip with the line items as properties, which kicks off the post-purchase nurture campaign that's already built in Drip's UI; or a HubSpot deal-stage change applies a tag in Drip that segments the contact into a different audience for the next send.

Connect Drip

No credit card required · Set up in under 2 minutes

0triggers

7actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything Drip can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs	Open action
Apply Tag	Adds a tag to a Drip subscriber. Tags drive Drip's automation triggers and segmentation — apply a tag to fire the matching workflow downstream in Drip itself.	2 inputs	View
Create Drip Subscriber	Creates or upserts a subscriber by email with custom fields, tags, and starting campaign. The base hook for "form submission → push to Drip" sync workflows in e-commerce email programs.	4 inputs	View
Find Subscriber by Email	Returns a subscriber by exact email match. The standard "find before update" pattern; returns 404 if no match, which workflows can branch on to decide create vs update.	1 input	View
Record Custom Event	Pushes a behavioural event tied to a subscriber. Drip campaigns can trigger on events for purchase-completion flows, abandoned-cart automations, post-trial conversions.	3 inputs	View
Remove Drip Tag	Removes a specific tag from a subscriber. For "campaign ended" or "qualification expired" state-exit transitions.	2 inputs	View
Tag Drip Subscriber	Alias for Apply Tag — adds a tag to a subscriber by email. For Drip's automation hooks where tag application is the trigger.	2 inputs	View
Track Drip Event	Logs a custom event for a subscriber with optional properties. Drives event-based campaign triggers in Drip's automation engine.	3 inputs	View

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Drip once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Drip field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Drip integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Drip to Tiny Command?

Open the Tiny Command workflow builder, drop in a Drip node, and click Connect. Authorize Drip once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Drip triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Drip today. Use Tiny Command's universal Webhook or Schedule trigger to start Drip workflows, then run any Drip action you need.

What Drip actions can I run from a workflow?

7 Drip actions are available out of the box, covering calendar & scheduling operations like "Apply Tag". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Drip integration real-time?

Drip actions execute synchronously inside your workflow. Tiny Command waits for Drip's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Drip with Tiny Command?

No. Every Drip trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Drip API endpoint directly.

How much does the Drip integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Drip integration itself has no per-app surcharge.

Drip integration

Do anything Drip can do, from a workflow.

Pre-built Drip workflows.

Three things worth knowing.

Questions about the Drip integration.

More calendar & scheduling apps people connect.

Do more with Drip.