Connect Jira to Altoviz

When something happens in Jira, Notis takes the next step in Altoviz. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Jira to Altoviz

View example

Turn Jira Product Requests into Altoviz Products

Create an Altoviz product from a Jira issue that contains a complete product request.

View example

Look Up Altoviz Customers from Jira Requests

Find an Altoviz customer by email when a new Jira issue includes a customer request or billing question.

View example

Apply Customer Detail Changes from Jira

Update an existing Altoviz customer's information when a Jira issue records a clear customer detail change.

View example

Find Altoviz Products Mentioned in Jira

Look up an Altoviz product by number when a new Jira issue includes that identifier.

View example

Prepare Altoviz Classifications for New Jira Projects

Retrieve Altoviz classifications when a new Jira project is added for work that needs accounting setup.

View example

Check Altoviz VAT Rates for Jira Tax Questions

Retrieve available Altoviz VAT rates when a Jira issue is updated with a tax or VAT question.

Supported Triggers and Actions

Notis builds workflows that link Jira to Altoviz. A trigger fires from one place; an action lands in another.

Jira triggers

Altoviz actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Create Product

Creates a new product in the altoviz system. this tool allows for the independent creation of a product with all necessary details.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Delete Product

This tool allows you to delete an existing product from altoviz. the action permanently removes the product from the system.

ActionInstant

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Find Contact by Email

This tool allows searching for contacts in altoviz using an email address. the action is independently executable and returns contact details if found.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Find Customer by Email

This tool allows you to find a customer in altoviz by their email address. this is a standalone action that doesn't require any resource ids or dependencies on other tools.

ActionInstant

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.

TriggerInstant

Find Product by Number

This tool allows users to find products in altoviz using the product number. it retrieves detailed product information including id, name, number, description, price, and other relevant metadata. it is a critical operation for product management in altoviz.

ActionInstant

Get Classifications List

This tool retrieves a list of classifications from the altoviz platform. classifications are essential for producing accounting registers from user-created invoices. it can fetch all classifications or filter them by type.

ActionInstant

Get Units List

This tool retrieves a list of all available units in the altoviz system. units are used for product measurements and quantity specifications in various transactions.

ActionInstant

Get VAT Rates

This tool retrieves a list of all available vat rates from altoviz. it's essential for creating and managing invoices and quotes where vat calculations are required. it supports retrieving vat rates, validating them for different regions, and ensuring correct tax calculations in financial documents.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.