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
Authentication
Authentication method: custom
Authentication profiles
connection · custom
- Account Name Required
- API Key Required · protected credential
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| 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 addressfullName· string · Optional, The contact's full namekind· string · Optional, The type of contactcountry· string · Required, 2-letter ISO country code (e.g., US, GB)city· string · Optional, City/District/Suburb/Town/VillagepostalCode· string · Optional, ZIP or postal coderegion· string · Optional, State/Province/RegionstreetLine1· string · Optional, Street address or PO BoxstreetLine2· string · Optional, Apartment/Suite/Unit/BuildingtaxId· string · Optional, Tax identification number (VAT, ABN, etc.)taxStatus· string · Optional, Tax status of the contactlanguage· string · Optional, 2-letter ISO language code (e.g., EN, FR, ES)phone· string · Optional, The contact's phone numberwebsite· string · Optional, The contact's website URLdiscount· number · Optional, Default discount for this contact (as a percentage)notes· string · Optional, Internal notes about the contactprocessorId· 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 namecontactLastName· string · Optional, The vendor's last name (optional for person contacts)contactEmail· string · Optional, The vendor's email addresscontactCountry· string · Required, 2-letter ISO country code (e.g., US, GB)itemDescription· string · Required, Description of the expense itemitemQuantity· number · Required, Quantity of the expense itemitemUnitCost· string · Required, Unit cost of the expense itempaymentMethod· string · Required, How the expense was paidcountry· string · Required, 2-letter ISO country code for the expense locationpoNumber· string · Optional, Purchase order number (optional)tagList· string · Optional, Tags for the expense, separated by commasnotes· 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 invoicedueDate· string · Optional, Date on which payment for this invoice is due (YYYY-MM-DD)customerFirstName· string · Required, The customer's first namecustomerLastName· string · Optional, The customer's last namecustomerEmail· string · Optional, The customer's email addresscustomerCountry· string · Optional, 2-letter ISO country code (e.g., US, GB)itemDescription· string · Required, Description of the invoice line itemitemQuantity· number · Required, Quantity of the invoice itemitemUnitCost· string · Required, Unit cost of the invoice itempoNumber· string · Optional, Purchase order numbertagList· 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 · Requiredmethod· string · Requiredheaders· object · Optional, Authorization headers are injected automatically from your connection.queryParams· object · Optional, Appended to the URL as ?key=value.body_type· string · Optionalbody· object · Optionalresponse_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
- Add the Quaderno connector to the workflow in the target Flows360 Studio instance.
- 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.
- 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.
- Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
- 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.