PPer-pair page

Connect Play.ht to Slack in two minutes.

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

Connect Play.ht and Slack See reverse direction

Trigger app

Play.ht as the trigger

Workflows fire when something happens in Play.ht.

Play.ht has no triggers yet. Use the catalog's universal Webhook trigger as the upstream.

Action app

Slack as the action

Workflows do something in Slack, instantly.

See all 45 actions →

Both directions

Pick the way that fits your stack.

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

PPlay.ht → Slack

When something happens in Play.ht, do it in Slack.

0 Play.ht triggers wired to 45 Slack actions.

PSlack → Play.ht

Or fire it the other way around.

13 Slack triggers wired to 3 Play.ht actions downstream.

See Slack → Play.ht →

Popular pairings

Common Play.ht → Slack workflows.

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

Showing 0 of 0 combinations

How it works

Connect Play.ht and Slack in five steps.

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

1
Connect
Authorize Play.ht and Slack
Open Tiny Command, authorize Play.ht and Slack once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Play.ht trigger
Drop the Play.ht → New event trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/playht.event
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
Action
Add the Slack action
Drop the Slack → Raw API Request action below it. Map fields from the Play.ht payload into the Slack inputs.
slack.api-request
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 Play.ht + Slack.

How long does it take to connect Play.ht and Slack on Tiny Command?

Under two minutes. Authorize Play.ht and Slack once each, drop the Play.ht trigger and Slack action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.

Is the Play.ht ↔ Slack integration real-time?

Yes. Both Play.ht and Slack 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 Play.ht and Slack?

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 Slack.

What Play.ht events can trigger a Slack workflow?

Use Tiny Command's universal Webhook trigger to receive Play.ht events, then run any of the 45 Slack actions downstream.

Do I need a paid plan to use Play.ht with Slack?

No. There's a free tier that covers most Play.ht+Slack use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.

What if I want Slack → Play.ht instead?

Build it the same way, in reverse. There's a dedicated /integrations/slack/with/playht page with the reverse-direction triggers and actions.

Other apps that pair well with Play.ht.

P+

Play.ht + Gmail

P+

Play.ht + Google Sheets

Spreadsheets & Databases