Slack Integration (Slack app in early access)
With the Re:port Flow Slack app ("Report Flow"), you pick a template from the /reportflow command, fill in the form that opens, and get a PDF. The PDF is posted to the channel where you ran the command (or sent to you by DM when it cannot be posted there).
The Slack app is in early access, before general release and before any Slack Marketplace listing. You will not find it in the Slack Marketplace (App Directory); install it directly from the install link on this page. It has not been reviewed or certified by Slack. While in early access, screens, steps and available actions may change.
What you can do
| Action | Description | Status |
|---|---|---|
/reportflow command | Pick a template from the connected Re:port Flow workspace and fill in a Slack form (modal) to create a PDF | Available |
| Receiving the PDF | The PDF is posted to the channel where you ran the command, with a mention of the requester and a receipt number. When run from a DM, or when the channel cannot be posted to, it is sent to you by DM | Available |
| Using it from Slackbot | Slackbot can connect to the Re:port Flow MCP server so you can ask for templates or PDFs in natural language. PDFs are not attached in Slack; you check them through a link to your generation history (sign-in required) | Available (whether you can use Slackbot depends on your Slack plan) |
The following are not available:
- Starting from a Slack message or shortcut (only the
/reportflowcommand) - Automatic creation on a schedule or triggered by events
- Posting as a thread reply, or sending to a different channel or person
- Output other than PDF (CSV, Excel), or several PDFs from one request
Before you start
- A Slack account that is an admin or owner of the Slack workspace. Only admins and owners can install the app and connect Re:port Flow (members and guests cannot)
- A Re:port Flow workspace and a Re:port Flow account that can generate PDFs in it (create one at re-port-flow.com)
- A template to generate from. If you do not have one, create it in Re:port Flow or copy one from the template gallery
Install and connect to Re:port Flow
Each Slack workspace connects once. After that, every member of the workspace can use /reportflow.
-
A Slack workspace admin or owner opens the Add to Slack button below (the install link https://slack.re-port-flow.com/slack/install)
-
In Slack, check the workspace and the permissions the app asks for, then choose Allow
-
The Re:port Flow sign-in screen opens. Sign in, choose the Re:port Flow workspace to use, and consent
-
When you see "Report Flow に接続しました" (connected to Report Flow), you are done. Close the page and return to Slack
The connection uses OAuth 2.0 (Authorization Code + PKCE) and asks for the Re:port Flow scopes openid, profile and pdf:generate (OAuth 2.0 > Scopes). You never paste an API key into Slack.
PDFs are generated with the permissions of the Re:port Flow account that consented during the connection. Whoever runs the command in Slack, the available templates and plan limits are those of that account and the chosen workspace.
Permissions the app asks Slack for
| Scope | Used for |
|---|---|
commands | Receiving the /reportflow command |
chat:write | Sending acknowledgements and error notices |
files:write | Uploading the PDF to the channel or DM |
im:write | Opening a DM with the requester |
users:read | Checking that the person connecting is an admin or owner, and that the person running the command is a workspace member |
channels:read / groups:read | Checking that the PDF may be posted to the channel (the app is a member, the channel is not shared with an external organization, and it is not archived) |
mcp:connect | Letting Slackbot connect to the Re:port Flow MCP server |
The app does not ask for permission to read your message history.
Usage (/reportflow)
- In the channel where you want to share the PDF (or in a DM with the Report Flow app), type
/reportflowand send it - Pick a template in the window that opens (up to 100 templates are listed)
- The template's fields appear as a form. Fill in the values. For line items (tables), use 行を追加 (add row) / 行を削除 (remove row) to change the number of rows
- Choose 送信 (submit). You will see "受け付けました" (received)
- When the PDF is ready, it is posted to the channel where you ran the command (or to your DM if you ran it from a DM)
To post to a channel, the Report Flow app must be a member of that channel. If it is not, the PDF and the reason are sent to your DM; add the app from the channel's Integrations tab. The app does not post to channels shared with external organizations (Slack Connect) or to archived channels; it sends the PDF to your DM instead.
Fields you can fill in
| Template field | Slack form |
|---|---|
| Text / URL | Text input |
| Number | Number input |
| Date | Date picker |
| Boolean | Choice of はい (yes) / いいえ (no) / 未指定 (unset) |
| Object (group) | Each field inside is shown as its own input |
| Line items (array) | Inputs for each column on each row. Rows can be added and removed |
These templates cannot be used from Slack. If you see a message that the template cannot be entered from Slack or has too many fields to fit, create the PDF in Re:port Flow instead:
- Line items nested inside line items (nested arrays)
- Line items or groups with no column / field definitions
- So many fields or rows that the Slack form's display limit is exceeded
The field definitions Re:port Flow returns do not include required, choice or default values, so the Slack form shows no required marks, choices or defaults. A field submitted empty is not sent at all, so the PDF shows whatever the template's design shows for it (usually blank). See Variable basics for how template fields work.
Using it from Slackbot
Installing the app lets Slackbot connect to the Re:port Flow MCP server (https://mcp.re-port-flow.com/mcp).
- In Slackbot, choose the Report Flow connection
- Sign in to Re:port Flow, choose a workspace and consent. This connection is per user, separate from the workspace-level connection used by
/reportflow - Ask Slackbot something like "Show me my Re:port Flow templates" or "Create a PDF from the invoice template"
- See MCP Server for the available tools and authentication
- PDFs are not attached in Slack. Check them through the generation history link in the generation tool's response (sign-in to Re:port Flow required). For async generation too, the link comes back in the generation tool's response together with the request ID. The status check (
get_generation_status; see workspace roles and tools) only tells you whether generation finished; it does not include the link - Whether you can use Slackbot, and its usage limits, depend on your Slack plan and admin settings
- To stop, disconnect from Slackbot's connection settings
Disconnect or switch
- Disconnect: uninstall the Report Flow app from Slack's app management screen. This deletes the Slack workspace's connection and any half-filled form records
- Switch to another Re:port Flow workspace / reconnect: an admin or owner goes through the install link again. The new connection replaces the previous one
Security and data handling
- Connection credentials are stored encrypted. The Slack bot token and the Re:port Flow tokens are stored encrypted on the Re:port Flow side and never appear in Slack screens or messages
- Half-filled form records are deleted within 24 hours. Entered values are not put in the Slack form's hidden field (
private_metadata) - Access is limited. Only members of the Slack workspace can use
/reportflow; guests and external Slack Connect users cannot - When Slack reports an uninstall or token revocation, the Slack workspace's connection is deleted
PDFs and entered data are also handled by Re:port Flow. See Security and data handling for storage location, retention and encryption. PDFs uploaded to Slack remain as Slack files and cannot be recalled by Re:port Flow.
Limitations
- Because it is in early access, screens, steps and available actions may change before general release
- The app's screens and messages are in Japanese
/reportflowhas one connection (one Re:port Flow workspace) per Slack workspace. You cannot use different Re:port Flow workspaces per channel or per user (the Slackbot connection is per user)- Org-wide installation on Enterprise Grid is not supported (install per workspace)
- One PDF per request
- Up to 100 templates are listed for selection
- PDF generation goes through the Re:port Flow API, so your workspace plan's output limits and request limits apply (Limitations)
Troubleshooting
"管理者による接続が必要です" (an admin must connect)
Only Slack workspace admins and owners can connect Re:port Flow. Send the install link to an admin or owner and ask them to complete it.
"インストールできませんでした" / "接続できませんでした" (install / connection failed)
Shown when too much time passed during the steps, the flow was continued in a different browser, or permission was not granted in Slack or Re:port Flow. Start again from the install link. If it says the permission needed to create PDFs was not granted, allow all permissions on the Re:port Flow consent screen.
/reportflow says the workspace is not connected to Re:port Flow yet
The Slack workspace has not been connected. Follow the message; an admin or owner needs to connect it.
It says the connection to Re:port Flow was lost
The token of the Re:port Flow account used for the connection is no longer valid, or that account lost its permissions in the workspace. An admin or owner should reconnect from the install link. If the PDF was already created but could not be delivered, do not request it again; get it from your Re:port Flow generation history.
It says only workspace members can use the app
Guests and users from external organizations joined through Slack Connect cannot use /reportflow.
No templates are listed
The cause depends on the message you see.
- "まだテンプレートがありません" (no templates yet): the connected Re:port Flow workspace has no templates. Create one in Re:port Flow or copy one from the gallery, then run the command again
- "ほか ○ 件のテンプレートは、ここには表示できません" (N more templates cannot be shown here) under the list: up to 100 templates are listed. If the template you want is not in the list, create the PDF in Re:port Flow instead
- "テンプレートは、Slack から選べる形ではありません" (templates cannot be picked from Slack): none of the templates can be picked from Slack. Create the PDF in Re:port Flow instead
It says the form expired or the template changed
Time passed since the form was opened, or the template was edited after you opened it. Run /reportflow again.
The PDF arrived in my DM instead of the channel
The DM explains why it was not posted to the channel. If the app is not a member of the channel, add it from the channel's Integrations tab. The app does not post to Slack Connect channels or archived channels.
It says the plan limit has been reached
The connected Re:port Flow workspace has reached its plan's output limit. Check your plan and usage.
It says it could not confirm whether the PDF was created or delivered
To avoid duplicates, the app does not retry automatically. Check that the PDF is not in the channel or your DM, then check your Re:port Flow generation history. Give the receipt number shown in the DM when you contact support.
Related pages
- Integration Overview — compare with other integrations
- MCP Server — tools and authentication used from Slackbot
- OAuth 2.0 — authorization flow and scopes
- Variable basics — how template fields work