Find the right Apilio automation for each new Jira issue
New work arrives in Jira. Get the current Apilio logicblocks in context before deciding what should happen next.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Action
Get Logicblocks
Tool to fetch all logicblocks of a user. use after authenticating with apilio api when you need to list available logicblocks.
Why this helps
A new issue can require a device or process automation, but finding the right existing logicblock adds another context switch.
- See the available Apilio logicblocks alongside new Jira work.
- Reduce manual searching when deciding how an issue should be handled.
- Keep automation decisions grounded in the logicblocks returned by Apilio.
Setup
Build it in a few focused steps.
- 1Connect Jira and Apilio once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel to create it; name it and describe the outcome.
- 3In one instruction, ask Notis to retrieve Apilio logicblocks and summarize which may be relevant to each new issue.
- 4Choose the Jira New Issue trigger, then choose where run reports should go.
- 5Test with one real Jira issue and review the report.
Questions about this workflow
Does this run for every Jira project?
No. The New Issue event fires only for issues created in the Jira project you configure.
Does this run an Apilio logicblock?
No. The available Apilio action retrieves logicblocks. Notis can summarize the returned list, but this action does not trigger one.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Apilio. A trigger fires from one place; an action lands in another.
Jira triggers
Apilio actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Boolean Variables
Tool to fetch all boolean variables. use when you need the full list of boolean variables and their current states.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Conditions
Tool to fetch all evaluatable conditions. use when you need to list available conditions.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Get Logicblocks
Tool to fetch all logicblocks of a user. use after authenticating with apilio api when you need to list available logicblocks.
New Project
Triggered when a new project is added in Jira
Get Numeric Variables
Tool to fetch all numeric variables. use after authenticating the apilio api.
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.
Get String Variables
Tool to fetch all string variables. use after authenticating the apilio api.
Connect any two apps with Notis in the middle.
Jira and Apilio, 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 Apilio.