Get Slack notifications for new Expensify reports.
When a new report is submitted in Expensify, send an alert notification to a specified Slack channel.
4.9/5 on G2·
Google for Startups Accelerator
How Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Expensify Explore Expensify →
TriggersFires when an employee submits a new expense in Expensify.
Fires when an expense in Expensify is approved.
Fires when an expense in Expensify is rejected.
Fires when a receipt is attached to an expense in Expensify.
Creates a new expense report in Expensify.
Approves a pending expense in Expensify.
Rejects a pending expense in Expensify.
Syncs an approved expense in Expensify to the general ledger.
Slack Explore Slack →
TriggersFires when a new message is posted to a channel in Slack.
Fires when your team or a keyword is mentioned in Slack.
Fires when a new channel is created in Slack.
Fires when a new file is shared in Slack.
Posts a message to a channel in Slack.
Sends a direct message to a person in Slack.
Creates a new channel in Slack.
Adds a user to a channel in Slack.
Common questions
Can Knit build “Get Slack notifications for new Expensify reports.” between Expensify and Slack?
Yes — describe it in the box above and Knit's Integrations Agent researches Expensify and Slack's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.