FINANCE

Slack receipt upload to Notion reimbursement tracker

Lets employees submit a receipt by uploading it in a Slack channel, parses it with OpenAI, and creates a tracked reimbursement entry in a Notion database with a status field.

CategoryFinance
Enginesim
Difficultybeginner
Triggerevent
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerReceipt uploaded to expenses Slack channelSlack
  • ActionRetrieve uploaded receipt file from SlackSlack
  • ActionExtract vendor, amount, and date with OpenAIOpenAI
  • ActionCreate Pending entry in Notion reimbursement databaseNotionNotion
  • OutputReply in Slack thread with confirmation and linkNotionNotion

What it does

Makes Slack the front door for expense submissions. When someone uploads a receipt image to the designated channel, the workflow reads it with OpenAI, captures the merchant, amount, and date, and creates a reimbursement record in a Notion database that finance can work through.

When to use it

Use this when your team already lives in Slack and you want zero-friction submission with a structured Notion backlog for finance to review and mark paid. Good for distributed teams without a formal expense tool.

How it works

  1. 1A file is uploaded to the expenses Slack channel, triggering the workflow.
  2. 2The workflow retrieves the uploaded receipt file from Slack.
  3. 3OpenAI vision extracts vendor, total, currency, and date from the receipt.
  4. 4A new page is created in the Notion reimbursement database with the parsed fields, the submitter, and a status of Pending.
  5. 5A threaded Slack reply confirms the submission and links to the new Notion entry.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SlackChannels, DMs, threads, mentions.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect NotionPages, databases, comments.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.