Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Katana

Katana is a cloud-based manufacturing ERP software for inventory, production, and order management.

CategoryProductivity
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Katana with Flows360

Katana is a cloud-based manufacturing ERP software for inventory, production, and order management.

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

Available actions

  • Create Customer
  • Create Sales Order
  • Find Customer
  • 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: Katana
  • Package: @activepieces/piece-katana@0.2.0
  • Exact artifact digest: sha256:a9cd6d4c71f9449bcad77743b6ad384d22b46e407c360e942532139c3fcfe511
  • 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 Customer (create_customer), Creates a new customer in Katana. Classification: read.
  • Create Sales Order (create_sales_order), Creates a new sales order in Katana. Classification: read.
  • Find Customer (find_customer), Find a customer by name, email, or phone number. 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 objects4
Supported actions4
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Customer Yes No Creates a new customer in Katana.
Create Sales Order Yes No Creates a new sales order in Katana.
Find Customer Yes No Find a customer by name, email, or phone number.
Custom API Call Yes No Make a custom API call to a specific endpoint

Supported actions

Create Customer · Read

Creates a new customer in Katana.

create_customer · Risk: low · Retry: safe

Inputs

  • name · string · Required, Customer display name.
  • first_name · string · Optional
  • last_name · string · Optional
  • company · string · Optional
  • email · string · Optional
  • phone · string · Optional
  • currency · string · Optional, Currency code (ISO 4217), e.g. USD, EUR, GBP.
  • reference_id · string · Optional, External reference ID (max 100 characters).
  • category · string · Optional, Customer category (max 100 characters).
  • comment · string · Optional, Additional notes about the customer.
  • discount_rate · number · Optional, Default discount rate for this customer.
  • addresses · array · Optional
Create Sales Order · Read

Creates a new sales order in Katana.

create_sales_order · Risk: low · Retry: safe

Inputs

  • order_no · string · Required, Unique order number.
  • customer_id · string · Required, Select the customer.
  • variant_id · string · Required, Select the product variant.
  • quantity · number · Required, Quantity for the product variant.
  • price_per_unit · number · Optional, Override price per unit.
  • total_discount · number · Optional, Discount amount for this line.
  • tax_rate_id · string · Optional
  • additional_order_rows · object · Optional, Add more line items as JSON array. Each object needs: variant_id, quantity. Optional: price_per_unit, total_discount, tax_rate_id, location_id.
  • status · string · Optional, Order status. Use PENDING for quotes.
  • location_id · string · Optional
  • currency · string · Optional, Currency code (ISO 4217), e.g. USD, EUR.
  • order_created_date · string · Optional
  • delivery_date · string · Optional
  • customer_ref · string · Optional, Customer reference number (max 255 characters).
  • additional_info · string · Optional, Additional notes for this order.
  • tracking_number · string · Optional, Shipping tracking number (max 256 characters).
  • tracking_number_url · string · Optional, URL to track the shipment.
  • addresses · array · Optional
  • ecommerce_order_type · string · Optional, Source platform (e.g. shopify).
  • ecommerce_store_name · string · Optional, Store identifier.
  • ecommerce_order_id · string · Optional, External order ID from the e-commerce platform.
Find Customer · Read

Find a customer by name, email, or phone number.

find_customer · Risk: low · Retry: safe

Inputs

  • name · string · Optional, Filters customers by name.
  • first_name · string · Optional, Filters customers by first name.
  • last_name · string · Optional, Filters customers by last name.
  • company · string · Optional, Filters customers by company.
  • email · string · Optional, Filters customers by email.
  • phone · string · Optional, Filters customers by phone number.
  • currency · string · Optional, Filters customers by currency.
  • reference_id · string · Optional, Filters customers by reference ID.
  • category · string · Optional, Filters customers by category.
  • include_deleted · boolean · Optional, Include soft-deleted customers in results.
  • limit · number · Optional, Maximum number of results to return (default is 50).
  • page · number · Optional, Page number for pagination (default is 1).
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 Katana 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-katana@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 4 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 Katana 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-katana@0.2.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.

github.com