Bring Apify run history into a Jira review
When an issue update asks for run history, retrieve runs for the identified Actor and include the results in the run report.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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
Checking whether an Actor has run recently can stall a review when run history lives in a separate tool.
- Bring run history into the ticket follow-up process.
- Reduce manual searches across Actor runs.
- Support investigation using available run records.
Setup
Build it in a few focused steps.
- 1Connect Jira and Apify once in the Notis portal.
- 2Create an automation in the portal or tell Notis in plain language.
- 3Describe how the issue identifies the Actor and which run history details are useful.
- 4Pick the Jira Updated Issue trigger and choose where run reports should go.
- 5Test with one real issue update that identifies an Actor for review.
Questions about this workflow
Does this retrieve task runs?
No. This action retrieves runs for a specified Actor. Use an Actor identifier in the issue or instruction.
Can it filter run results?
The action supports pagination and optional status filtering. Describe the status of interest if the review needs one.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Apify. A trigger fires from one place; an action lands in another.
Jira 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.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
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.
New Project
Triggered when a new project is added in Jira
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.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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.
Delete Webhook
Tool to delete a webhook by its id. use when removing a webhook after confirming the webhook id.
Get Actor Details
Tool to get details of a specific actor. use when you need actor metadata by id or username/actorname.
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.
Jira 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.