Drip
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.
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 |
|---|---|
| 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. |
| 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. |
| 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. |
| 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. |
| Remove Drip Tag | Removes a specific tag from a subscriber. For "campaign ended" or "qualification expired" state-exit transitions. |
| 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. |
| Track Drip Event | Logs a custom event for a subscriber with optional properties. Drives event-based campaign triggers in Drip's automation engine. |
Pre-built Drip workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Drip once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Drip field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
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?
What Drip triggers does Tiny Command support?
What Drip actions can I run from a workflow?
Is the Drip integration real-time?
Do I need to write code to use Drip with Tiny Command?
How much does the Drip integration cost?
More calendar & scheduling apps people connect.
Same category as Drip, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Drip.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
