Apply the right Carbone API version for changing work
Keep the Carbone request version consistent as Jira work moves forward.
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
Set Carbone API Version
Tool to set the carbone api version to be used for subsequent requests. use before rendering or managing templates to ensure correct version is applied.
Why this helps
An automation can behave unpredictably when its Carbone API version is not set as expected.
- Set the requested API version during an issue update run.
- Keep subsequent Carbone calls aligned with the version you specify.
- Reduce version setup repetition.
Setup
Build it in a few focused steps.
- 1Connect Jira and Carbone once in the Notis portal.
- 2Create an automation and state the Carbone API version to set when an issue changes.
- 3Pick the Jira Updated Issue trigger.
- 4Choose where Notis should send run reports.
- 5Test with one real issue update and check the run report.
Questions about this workflow
Which version will Notis set?
Specify the Carbone API version in your instruction. This action sets the version for subsequent requests.
Does setting the version create a report?
No. It configures the version to be used by later Carbone requests.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Carbone. A trigger fires from one place; an action lands in another.
Jira triggers
Carbone actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Carbone Template
Tool to delete a template from the carbone server. use after confirming you have the correct template id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Download Template
Tool to download a template from carbone by template id. use when you need to retrieve the original template file.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Generate Carbone Report
Tool to generate a carbone report from a template and json data. use when you need to render documents in various formats.
New Project
Triggered when a new project is added in Jira
Generate Template ID
Tool to generate a unique template id for a new template. use when you need the template identifier before uploading.
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 Carbone Server Status
Tool to retrieve the current status and health of the carbone server. use before generating reports to ensure the service is operational.
Set Carbone API Version
Tool to set the carbone api version to be used for subsequent requests. use before rendering or managing templates to ensure correct version is applied.
Upload a template
Tool to upload a template to the carbone server. use when you need to add or replace a template by providing its content.
Connect any two apps with Notis in the middle.
Jira and Carbone, 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 Carbone.