Failed Actor Run Urgent Alerts
Failed research runs create urgent Linear issues automatically so nothing slips through.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get list of runs
Tool to get a list of runs for a specific actor. use when you need to paginate through runs and optionally filter by status before processing run data.
Why this helps
Failed Apify runs go unnoticed until you check the dashboard, leaving your team waiting for data that will never arrive.
- Failures are caught immediately
- Urgent issues created automatically
- No silent failures
- Team knows right away when data collection fails
Setup
Build it in a few focused steps.
- 1Connect Linear and Apify.
- 2Go to Automations > New Automation and write: Every morning, get a list of all Apify runs from yesterday and create an urgent Linear issue for any that failed.
- 3Select Daily Cron as the trigger and pick your morning time.
- 4Choose your channel and click Create.
- 5Monitor the urgent issues that get created when runs fail.
Questions about this workflow
Will this create an issue for every failed run?
Yes, unless you refine it in your prompt: Only create issues for critical actors or Only for runs that failed after retries.
Can I customize the urgency level?
Yes, ask Notis to create issues with specific labels or assignees: Create urgent issues and assign to the ops team.
How far back does the check look?
By default it checks the previous day. You can change this: Check the last 48 hours of runs.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Apify. A trigger fires from one place; an action lands in another.
Linear triggers
Apify actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Actor
Tool to create a new actor with specified configuration. use when you need to initialize a fresh actor programmatically before publishing or running it.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Dataset
Tool to create a new dataset. use when you need to initialize or retrieve a dataset by name.
Comment Received Trigger
Triggered when a comment is received.
Create Actor Task
Tool to create a new actor task with specified settings. use when you need to configure or schedule recurring actor runs programmatically.
Issue Created Trigger
Triggered when a new issue is created.
Create Task Webhook
Tool to create a webhook for an actor task. use when you need external notifications about task run events (e.g., completion or failure) in downstream systems.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Delete Actor
Tool to delete an actor permanently. use when you need to remove an actor by its id or username~actorname. confirm before calling.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Delete Webhook
Tool to delete a webhook by its id. use when removing a webhook after confirming the webhook id.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Get Actor Details
Tool to get details of a specific actor. use when you need actor metadata by id or username/actorname.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Get all webhooks
Tool to get a list of all webhooks created by the user. use when you need to enumerate webhooks before filtering or maintenance.
Connect any two apps with Notis in the middle.
Linear and Apify, 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 Apify.