Runscope runs Radar tests against your APIs on a schedule. FlowMattic takes each completed test run and posts it to Slack, so failing assertions reach the engineer on call and passing runs stay quiet if you prefer. For API teams who want test results where they already discuss incidents.
1 trigger 14 actions 6 example workflows 2 ready-made templates Unlimited runs
When this happens in Runscope1 trigger
Do this in Slack14 actions
1. TriggerNew Completed Radar Test Run2. ActionSend Channel MessageWhen Runscope fires New Completed Radar Test Run, FlowMattic runs Send Channel Message in Slack with the data from that event.
You build this in the FlowMattic workflow builder on your own site. See the setup steps
Each one uses only triggers and actions the two integrations ship today, plus FlowMattic's own tools. Where the library has a ready-made template, import it instead of building from scratch.
Ready-made templateEach run shows the test name, result and a link to the details, giving the API team a running history of checks in one channel.
New Completed Radar Test RunSend Channel Message
View the template A Filter on the run result keeps passing runs out of Slack, so the channel lights up only when an assertion breaks and people take it seriously.
New Completed Radar Test RunFilterSend Channel Message
Failures also go as a direct message to the on-call engineer's Slack user, so a broken checkout API gets attention even if nobody is reading the channel.
New Completed Radar Test RunFilterFind User by EmailSend Direct Message
A Router reads the test or bucket name and posts payments tests to the payments channel and search tests to the search channel, so each team owns its checks.
New Completed Radar Test RunRouterSend Channel Message
Set Channel Topic writes the last result and run time into the topic, so anyone opening the channel sees at a glance whether the API is passing.
New Completed Radar Test RunDate/Time FormatterSet Channel Topic
An AI Agent reads the failed assertions and writes a short summary of what broke, posted with the run link, which helps support staff who do not read raw responses.
New Completed Radar Test RunAI AgentSend Channel Message
At the end, each completed Runscope Radar test run posts its result and link to your Slack channel.
Under Connects in FlowMattic, add a Slack connection for your engineering workspace.
Create a workflow with Runscope and New Completed Radar Test Run, then follow the trigger's instructions to send test run results to the workflow.
Trigger a Radar test run in Runscope so FlowMattic captures the result fields.
Add Send Channel Message, choose the channel, include the test name, result and link, test the step and switch the workflow on.
1. Trigger in Runscope
New Completed Radar Test Run
2. Action in Slack
Send Channel Message
Fields mapped from the earlier steps (a typical setup)
| From Runscope | To Slack |
|---|---|
| Test name | Message: test |
| Result | Message: pass or fail |
| Environment | Message: environment |
| Test run URL | Message: details |
A trigger starts a workflow. An action is something FlowMattic does in the app as a step.
Runscope and Slack connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
Failed runs go to the channel and to the on-call engineer, so a broken endpoint is looked at rather than logged.
Routing by test name gives every service team a channel with only the checks they own.
FlowMattic runs on your own WordPress site with unlimited runs, so tests every few minutes add no per-task charge.
Create a FlowMattic workflow with the Runscope New Completed Radar Test Run trigger, follow its instructions to point Runscope at the workflow, then add Slack Send Channel Message with the test name, result and link.
Yes. Add a Filter after the trigger that continues only when the result is a failure. Passing runs stop at the Filter and nothing is posted.
Yes. After the Filter, use Create Channel with the test name and date, then Invite User To Channel for the engineers who own the API.
Yes. Use a Router: failures post to Slack, and passing runs go to WP Tables on your site, giving you a history to check later without channel noise.
Yes. Add a Counter after the failure Filter and include the count in the message, so the channel shows whether a problem is a one-off or repeating.
Did not find your answer? You can browse the help center or ask us directly.
Slack and Google Sheets149 shared templates
Slack and Airtable44 shared templates
Slack and Fluent Forms42 shared templates
Slack and FluentCRM35 shared templates
Slack and ClickUp28 shared templates
Slack and Fluent Support21 shared templates
Slack and WooCommerce18 shared templates
Slack and Notion17 shared templatesInstall FlowMattic, connect both accounts and import a template. Every run stays on your own server.
30-day money-back guarantee Unlimited workflows and runs Self-hosted
Reviewed 27 Oct 2026. The example workflows are written with AI from the real triggers and actions of both integrations and checked against them. Runscope integration 1.0.0, Slack integration 1.0.
