Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

JustInvoice

Create and manage invoices with JustInvoice API

CategoryOther
Authenticationcustom
Version0.0.8
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect JustInvoice with Flows360

Create and manage invoices with JustInvoice API

Use the JustInvoice connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and no declared triggers.

Available actions

  • Create Invoice
  • Get Invoice
  • Mark Invoice Final
  • Mark Invoice Cancelled
  • Mark Invoice Paid
  • Delete Invoice

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: JustInvoice
  • Package: @activepieces/piece-just-invoice@0.0.8
  • Exact artifact digest: sha256:a932136dd7b016d12574ce16df6e9de70969f7e7a7b61ca507bbf652913cd67f
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Invoice (create_invoice), Creates a new invoice in JustInvoice Classification: read.
  • Get Invoice (get_invoice), Gets detailed information about a specific invoice Classification: read.
  • Mark Invoice Final (mark_invoice_final), Marks an invoice currently in draft as final and ready to accept payment Classification: read.
  • Mark Invoice Cancelled (mark_invoice_cancelled), Marks an invoice currently in final as cancelled Classification: read.
  • Mark Invoice Paid (mark_invoice_paid), Marks an existing final invoice as paid Classification: read.
  • Delete Invoice (delete_invoice), Permanently deletes an invoice Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects6
Supported actions6
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Invoice Yes No Creates a new invoice in JustInvoice
Get Invoice Yes No Gets detailed information about a specific invoice
Mark Invoice Final Yes No Marks an invoice currently in draft as final and ready to accept payment
Mark Invoice Cancelled Yes No Marks an invoice currently in final as cancelled
Mark Invoice Paid Yes No Marks an existing final invoice as paid
Delete Invoice Yes No Permanently deletes an invoice

Supported actions

Create Invoice · Read

Creates a new invoice in JustInvoice

create_invoice · Risk: low · Retry: safe

Inputs

  • customerEmail · string · Required, Email address of the customer
  • customerFirstName · string · Optional, First name of the customer
  • customerLastName · string · Optional, Last name of the customer
  • customerCompanyName · string · Optional, Company name of the customer
  • customerAddress · string · Optional, Street address of the customer
  • customerCity · string · Optional, City of the customer
  • customerProvinceState · string · Optional, Province or state of the customer
  • customerPostalCode · string · Optional, Postal code of the customer
  • customerCountry · string · Optional, Country code of the customer (e.g., US, CA)
  • invoiceDate · string · Optional, Date of the invoice
  • invoiceStatus · string · Optional, Initial status of the invoice
  • currencyCode · string · Optional, Currency code (e.g., USD, EUR)
  • noteToCustomer · string · Optional, Additional notes for the customer
  • lineItems · array · Required, Products or services being billed
Get Invoice · Read

Gets detailed information about a specific invoice

get_invoice · Risk: low · Retry: safe

Inputs

  • invoiceId · string · Required, The ID or invoice number of the invoice to retrieve
Mark Invoice Final · Read

Marks an invoice currently in draft as final and ready to accept payment

mark_invoice_final · Risk: low · Retry: safe

Inputs

  • invoiceId · string · Required, The ID or invoice number of the invoice to mark as final
Mark Invoice Cancelled · Read

Marks an invoice currently in final as cancelled

mark_invoice_cancelled · Risk: low · Retry: safe

Inputs

  • invoiceId · string · Required, The ID or invoice number of the invoice to mark as cancelled
Mark Invoice Paid · Read

Marks an existing final invoice as paid

mark_invoice_paid · Risk: low · Retry: safe

Inputs

  • invoiceId · string · Required, The ID or invoice number of the invoice to mark as paid
Delete Invoice · Read

Permanently deletes an invoice

delete_invoice · Risk: low · Retry: safe

Inputs

  • invoiceId · string · Required, The ID or invoice number of the invoice to delete

Setup

Setup

  1. Add the JustInvoice connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-just-invoice@0.0.8; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required JustInvoice connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-just-invoice@0.0.8 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com