OtherReal-timeUpdated May 2026

Vero

Vero behavioural messaging

Vero is the behavioural messaging platform — event-driven email + push notifications for SaaS and consumer apps, focused on lifecycle and re-engagement campaigns. Tiny Command exposes one action, no triggers (Vero emits engagement events via webhooks; configure pointing at a Tiny Command webhook trigger URL): List Items (recent events or subscribers depending on parameters). The connection uses a Vero API key. For SaaS workflows that need event-driven messaging similar to Customer.io or Iterable, Vero is a competitor in the same space — strong on push notifications for mobile apps, friendly developer DX. For new green-field, evaluate Vero alongside Customer.io, Iterable, and the newer entrants (Loops). For existing Vero-integrated workflows, this connector handles the integration layer.

Connect Vero

0triggers

1action

≈ 2 minto set up

Freetier · no card

Actions

Do anything Vero 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
List Items	Generic list endpoint for Vero resources. Choose the resource and Vero returns the matching items.	0 fields	View →

Recipes

Pre-built Vero workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Vero → Slack alerts

AI-triage every Vero event, ping the right channel only when it matters.

Vero → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Vero → Notion database

Turn Vero into a Notion-backed source of truth, auto-tagged.

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 Vero 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 Vero 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 Vero integration.

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

How do I connect Vero to Tiny Command?

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

What Vero triggers does Tiny Command support?

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

What Vero actions can I run from a workflow?

1 Vero action are available out of the box, covering other operations like "List Items". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Vero integration real-time?

Vero actions execute synchronously inside your workflow. Tiny Command waits for Vero'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 Vero with Tiny Command?

No. Every Vero 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 Vero API endpoint directly.

How much does the Vero 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 Vero integration itself has no per-app surcharge.