Check delivery proof images with recipient context
Keep the visual proof and recipient contact check together, so an exception is easier to review and route without rebuilding context.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Run Workflow
Tool to run a workflow specification with provided inputs. Use when you need to execute a custom Roboflow workflow pipeline for image processing, model inference, or other computer vision tasks.
Why this helps
Delivery exceptions demand fast attention, but the image and recipient details often need to be gathered from separate places.
- Run a submitted proof image through a specified Roboflow workflow.
- Assess the recipient number for invalid or disconnected line signals.
- Give exception review a consistent image and contact context.
Setup
Build it in a few focused steps.
- 1Connect Realphonevalidation and Roboflow to Notis once in the portal.
- 2Create an automation in Automations or describe the desired result to Notis in plain language.
- 3Use one instruction asking Notis to assess the recipient phone and run the submitted proof image through the chosen Roboflow workflow.
- 4Choose an incoming webhook trigger and a channel for run reports.
- 5Test with one actual proof image and recipient record.
Questions about this workflow
Does this decide whether delivery succeeded?
It returns the result of your configured image workflow and phone assessment; your process should interpret those results.
What starts the run?
Your delivery system or custom backend sends an HTTP request to the Notis webhook.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Realphonevalidation to Roboflow. A trigger fires from one place; an action lands in another.
Realphonevalidation triggers
Roboflow actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Describe Workflow Interface
Tool to describe the interface of a workflow specification. Use when you need to understand the inputs, outputs, and types for a Roboflow workflow definition.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Execution Engine Versions
Tool to retrieve available Execution Engine versions from Roboflow workflows API. Use when you need to check which execution engine versions are supported for workflow processing.
Get Server Info
Tool to retrieve information about the Roboflow inference server. Use when you need to check the server version, name, or unique identifier.
Get Server Metrics
Tool to retrieve Prometheus metrics from the Roboflow inference server. Use when monitoring server performance, tracking inference statistics, or debugging server health issues.
Get Workflow Schema
Tool to fetch the workflows block schema from Roboflow. Use when you need to retrieve the complete schema definition for workflow blocks.
Run Workflow
Tool to run a workflow specification with provided inputs. Use when you need to execute a custom Roboflow workflow pipeline for image processing, model inference, or other computer vision tasks.
Validate Workflow
Tool to validate a Roboflow workflow specification before execution. Use this to check if your workflow definition is syntactically correct and properly structured.
Connect any two apps with Notis in the middle.
Realphonevalidation and Roboflow, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Roboflow.