EmailReal-timeUpdated June 2026

Front integration

Front (App) shared inbox messaging

Front (this connector instance, distinct from the main front slug) exposes Front's shared inbox API for inbound conversation management — focused on the read-side and message-sending. Two actions, no triggers (Front Rules in admin handle event-driven workflows pointing at a Tiny Command webhook trigger URL): List Conversations (paginated history with filters by inbox, status, tag, assignee), Send Message (post a reply on an existing conversation, public or internal). The connection uses a Front API token from developer settings. For workflows that need richer Front interaction (add internal comments, update conversation status, manage tags), use the primary front connector which has broader action coverage. This connector is the simpler subset for "read conversations + send replies" workflows.

Connect Front

No credit card required · Set up in under 2 minutes

0triggers

2actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything Front 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
List Front Conversations	Paginated conversations with filters by inbox, status, assignee, tag. Useful for triage workflows and for capacity-planning dashboards.	2 inputs	View
Send Front Message	Posts a reply on a Front conversation. For new conversations on the same channel as previous interactions, Front routes via the existing channel automatically.	4 inputs	View

Recipes

Pre-built Front workflows.

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

Front → Slack alerts

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

Front → Google Sheets log

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

Front → Notion database

Turn Front 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 Front 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 Front 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 Front integration.

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

How do I connect Front to Tiny Command?

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

What Front triggers does Tiny Command support?

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

What Front actions can I run from a workflow?

2 Front actions are available out of the box, covering email operations like "List Front Conversations". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Front integration real-time?

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

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

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