Skip to content
← Back to documentation
Technical Reference

Quaderno

Quaderno is a tax software that handles sales tax, VAT, and GST for your online business. Automatically calculates tax, sends receipts and invoices, and provides instant multi-channel tax reports for your sales around the world.

CategoryCommerce
Authenticationcustom
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect Quaderno with Flows360

Quaderno is a tax software that handles sales tax, VAT, and GST for your online business. Automatically calculates tax, sends receipts and invoices, and provides instant multi-channel tax reports for your sales around the world.

Use the Quaderno 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 5 actions and no declared triggers.

Available actions

  • Create Contact
  • Find Contact
  • Create Expense
  • Create Invoice
  • Custom API Call

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: Quaderno
  • Package: @activepieces/piece-quaderno@0.1.0
  • Exact artifact digest: sha256:3efef7280820568373f496c5350b80a666f9cf99dc4fe2b84bea60e4d12dd09d
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. 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 Contact (createContact), Create a new contact in Quaderno (customer or vendor) Classification: read.
  • Find Contact (findContact), Search and list contacts from Quaderno Classification: read.
  • Create Expense (createExpense), Create a new expense in Quaderno Classification: read.
  • Create Invoice (createInvoice), Create a new invoice in Quaderno Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint 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 objects5
Supported actions5
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Account Name Required
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Contact Yes No Create a new contact in Quaderno (customer or vendor)
Find Contact Yes No Search and list contacts from Quaderno
Create Expense Yes No Create a new expense in Quaderno
Create Invoice Yes No Create a new invoice in Quaderno
Custom API Call Yes No Make a custom API call to a specific endpoint

Supported actions

Create Contact · Read

Create a new contact in Quaderno (customer or vendor)

create_contact · Risk: low · Retry: safe

Inputs

  • firstName · string · Required, The contact's first name (required for person contacts)
  • lastName · string · Optional, The contact's last name (optional)
  • email · string · Optional, The contact's email address
  • fullName · string · Optional, The contact's full name
  • kind · string · Optional, The type of contact
  • country · string · Required, 2-letter ISO country code (e.g., US, GB)
  • city · string · Optional, City/District/Suburb/Town/Village
  • postalCode · string · Optional, ZIP or postal code
  • region · string · Optional, State/Province/Region
  • streetLine1 · string · Optional, Street address or PO Box
  • streetLine2 · string · Optional, Apartment/Suite/Unit/Building
  • taxId · string · Optional, Tax identification number (VAT, ABN, etc.)
  • taxStatus · string · Optional, Tax status of the contact
  • language · string · Optional, 2-letter ISO language code (e.g., EN, FR, ES)
  • phone · string · Optional, The contact's phone number
  • website · string · Optional, The contact's website URL
  • discount · number · Optional, Default discount for this contact (as a percentage)
  • notes · string · Optional, Internal notes about the contact
  • processorId · string · Optional, The ID assigned by an external payment processor (e.g., Stripe customer ID)
  • processor · string · Optional, The external platform where the contact was imported from (e.g., stripe)
Find Contact · Read

Search and list contacts from Quaderno

find_contact · Risk: low · Retry: safe

Inputs

  • searchQuery · string · Optional, Search for contacts by name, email, or tax ID (optional)
  • processorId · string · Optional, Filter by processor ID (optional)
  • limit · number · Optional, Maximum number of results to return (default: 25, max: 100)
Create Expense · Read

Create a new expense in Quaderno

create_expense · Risk: low · Retry: safe

Inputs

  • issueDate · string · Required, Date when the expense was issued (YYYY-MM-DD)
  • currency · string · Required, 3-letter ISO currency code (USD, EUR, GBP, etc.)
  • contactFirstName · string · Required, The vendor's first name
  • contactLastName · string · Optional, The vendor's last name (optional for person contacts)
  • contactEmail · string · Optional, The vendor's email address
  • contactCountry · string · Required, 2-letter ISO country code (e.g., US, GB)
  • itemDescription · string · Required, Description of the expense item
  • itemQuantity · number · Required, Quantity of the expense item
  • itemUnitCost · string · Required, Unit cost of the expense item
  • paymentMethod · string · Required, How the expense was paid
  • country · string · Required, 2-letter ISO country code for the expense location
  • poNumber · string · Optional, Purchase order number (optional)
  • tagList · string · Optional, Tags for the expense, separated by commas
  • notes · string · Optional, Additional notes about the expense
Create Invoice · Read

Create a new invoice in Quaderno

create_invoice · Risk: low · Retry: safe

Inputs

  • issueDate · string · Required, Date when the invoice was issued (YYYY-MM-DD)
  • currency · string · Required, 3-letter ISO currency code (USD, EUR, GBP, etc.)
  • invoiceNumber · string · Optional, A unique, sequential code that identifies the invoice
  • dueDate · string · Optional, Date on which payment for this invoice is due (YYYY-MM-DD)
  • customerFirstName · string · Required, The customer's first name
  • customerLastName · string · Optional, The customer's last name
  • customerEmail · string · Optional, The customer's email address
  • customerCountry · string · Optional, 2-letter ISO country code (e.g., US, GB)
  • itemDescription · string · Required, Description of the invoice line item
  • itemQuantity · number · Required, Quantity of the invoice item
  • itemUnitCost · string · Required, Unit cost of the invoice item
  • poNumber · string · Optional, Purchase order number
  • tagList · string · Optional, Tags attached to the invoice (comma-separated)
  • notes · string · Optional, Extra notes about the invoice
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Setup

Setup

  1. Add the Quaderno 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:
  • Account Name (account_name), required.
  • API Key (api_key), required; stored as a sensitive connection value.
  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-quaderno@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 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 Quaderno 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-quaderno@0.1.0 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.