Skip to content
Notis

Check Carbone server status before reporting from Algodocs data

Know whether Carbone is reporting healthy before you start a batch of document-based reports.

Trigger

Recurring schedule

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

Action

Get Carbone Server Status

Checks the server’s current status and health.

Why this helps

Starting a reporting batch without checking the rendering service can leave you discovering a problem only after the work is queued.

  • Check Carbone health as part of a repeatable reporting routine.
  • See the service status before kicking off document generation.
  • Keep a readiness summary alongside the reporting context.

Setup

Build it in a few focused steps.

  • 1Connect Algodocs and Carbone once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a name.
  • 3Tell Notis to review the available Algodocs reporting context and retrieve Carbone server status before the planned report run.
  • 4Pick a recurring schedule as the trigger and choose where run reports should go.
  • 5Test with one real reporting cycle and review the status summary.

Questions about this workflow

Does this workflow generate reports?

No. It checks the Carbone server status and reports readiness context. Use a separate workflow with a report generation action to render documents.

Does Algodocs start this check when a document is processed?

No. Algodocs has no trigger events in this package. The check runs on your Notis schedule.

Does a healthy status guarantee my report will render?

No. It indicates the server status returned by Carbone at check time. Template validity and report data can still affect rendering.

When this happens · Trigger

Do this · Action

Checks the server’s current status and health.

Supported Triggers and Actions

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

Algodocs triggers

Carbone actions

Recurring trigger

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

TriggerScheduled

Delete Carbone Template

Deletes a Carbone template or version; the file is removed after a storage retention delay.

ActionInstant

Webhook trigger

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

TriggerInstant

Download Template

Downloads the original template file.

ActionInstant

Generate Carbone Report

Generates a report from a Carbone template and JSON data, and returns its render ID.

ActionInstant

Get Carbone Server Status

Checks the server’s current status and health.

ActionInstant

List Templates

Retrieves templates stored in the workspace.

ActionInstant

Set Carbone API Version

Sets the Carbone API version for subsequent requests.

ActionInstant

List Template Categories

Lists categories used to organize deployed Carbone templates.

ActionInstant

Upload a template

Uploads a template for document generation.

ActionInstant

Connect any two apps with Notis in the middle.

Algodocs and Carbone, or any other combination from 1,600+ 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.