Per-pair page

Connect Slack to Firecrawl in two minutes.

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

Trigger app
Slack as the trigger

Workflows fire when something happens in Slack.

See all 13 triggers →
Action app
Firecrawl as the action

Workflows do something in Firecrawl, instantly.

Connect Slack to Firecrawl — start free
Both directions

Pick the way that fits your stack.

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

Slack → Firecrawl

When something happens in Slack, do it in Firecrawl.

13 Slack triggers wired to 8 Firecrawl actions. Most-used pairing: App Home Opened → Crawl Site.

Firecrawl → Slack

Or fire it the other way around.

0 Firecrawl triggers wired to 45 Slack actions downstream.

  • Use any trigger in the catalog as the upstream.
See Firecrawl → Slack →
Popular pairings

Common Slack → Firecrawl workflows.

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

Showing 9 of 104 combinations
When app home opened in Slack, crawl site in Firecrawl.

Fires when a user opens your Slack app's Home tab or DM. Useful for refreshing the Home view, lazy-loading user-specific data, or tracking app engagement.

When app home opened in Slack, extract structured data in Firecrawl.

Fires when a user opens your Slack app's Home tab or DM. Useful for refreshing the Home view, lazy-loading user-specific data, or tracking app engagement.

When app home opened in Slack, get firecrawl agent result in Firecrawl.

Fires when a user opens your Slack app's Home tab or DM. Useful for refreshing the Home view, lazy-loading user-specific data, or tracking app engagement.

When app home opened in Slack, get crawl status in Firecrawl.

Fires when a user opens your Slack app's Home tab or DM. Useful for refreshing the Home view, lazy-loading user-specific data, or tracking app engagement.

When app mentioned in Slack, crawl site in Firecrawl.

Fires when your Slack app is mentioned in a message. The standard hook for chatbots that answer when summoned with @your-app.

When app mentioned in Slack, extract structured data in Firecrawl.

Fires when your Slack app is mentioned in a message. The standard hook for chatbots that answer when summoned with @your-app.

When app mentioned in Slack, get firecrawl agent result in Firecrawl.

Fires when your Slack app is mentioned in a message. The standard hook for chatbots that answer when summoned with @your-app.

When app mentioned in Slack, get crawl status in Firecrawl.

Fires when your Slack app is mentioned in a message. The standard hook for chatbots that answer when summoned with @your-app.

When new channel in Slack, crawl site in Firecrawl.

Fires when a new Slack channel is created in the workspace. Useful for auto-adding the bot, welcome messages, or governance audit logs.

How it works

Connect Slack and Firecrawl in five steps.

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

  1. 1
    Connect
    Authorize Slack and Firecrawl

    Open TinyCommand, authorize Slack and Firecrawl once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Slack trigger

    Drop the Slack → App Home Opened trigger onto the canvas. TinyCommand auto-registers the webhook.

    POST /v1/webhooks/slack.trigger-app-home-opened
  3. 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. 4
    Action
    Add the Firecrawl action

    Drop the Firecrawl → Crawl Site action below it. Map fields from the Slack payload into the Firecrawl inputs.

    firecrawl.crawl
  5. 5
    Publish
    Publish and forget

    Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Slack + Firecrawl.

How long does it take to connect Slack and Firecrawl on TinyCommand?
Under two minutes. Authorize Slack and Firecrawl once each, drop the Slack trigger and Firecrawl action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Slack ↔ Firecrawl integration real-time?
Yes. Both Slack and Firecrawl 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 Slack and Firecrawl?
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 Firecrawl.
What Slack events can trigger a Firecrawl workflow?
Any of the 13 Slack triggers, including "App Home Opened". Each fires in real time when the matching event happens in Slack.
Do I need a paid plan to use Slack with Firecrawl?
No. Both integrations come on every plan, including Free, which includes 1,000 credits a month with no credit card. Each workflow step uses 1 credit, and paid plans include more credits and team seats when you need them.
What if I want Firecrawl → Slack instead?
Build it the same way, in reverse. There's a dedicated /integrations/firecrawl/with/slack page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Slack.


Connect Slack to Firecrawl — start free