Look up the Bolna execution behind an incident
Put exact execution evidence beside the incident context.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get execution by id
Retrieve specific execution by `execution id`
Why this helps
Incident reviews drag when records must be copied manually from another platform.
- Speeds evidence gathering
- Keeps scope to one execution
- Produces a concise brief
Setup
Build it in a few focused steps.
- 1Connect 1Password and Bolna.
- 2Create an automation to retrieve the execution id in the request.
- 3Choose a Notis webhook and report channel.
- 4Test with one noncritical execution.
Questions about this workflow
Can it handle several ids?
Provide the ids and request separate lookups or a comparison.
Does it make a security determination?
It summarizes returned data against your stated criteria.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 1password to Bolna. A trigger fires from one place; an action lands in another.
1password triggers
Bolna actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete agent by id
Delete an agent
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete batch by id
Delete a batch
Fetch all batches by agent id
List all batches for agent
Get all agents
List all agents
Get all phone numbers
List all phone numbers for your account
Get execution by id
Retrieve specific execution by `execution id`
Make a phone call from agent
Initiate calls
Retrieve agent by id
Retrieve an agent
Connect any two apps with Notis in the middle.
1password and Bolna, 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 Bolna.