Overview
Connect Cartloom with Flows360
Sell products beautifully
Use the Cartloom 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 8 actions and no declared triggers.
Available actions
- Get Products
- Get Order
- Create Discount
- Get Discount
- Get All Discounts
- Get Order by Date
- Get Order by Email
- 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: Cartloom
- Package:
@activepieces/piece-cartloom@0.2.0 - Exact artifact digest:
sha256:e67c845935483fb270e43f9a3284a004fa5bf978df626268d70eb560e2065ffb - 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
- Get Products (
get_products), Get a list of products from Cartloom Classification: read. - Get Order (
get_order), Get an order from Cartloom Classification: read. - Create Discount (
create_discount), Create a discount in Cartloom Classification: read. - Get Discount (
get_discount), Get discount info from Cartloom Classification: read. - Get All Discounts (
get_all_discounts), Get a list of discounts from Cartloom Classification: read. - Get Order by Date (
get_orders_by_date), Get a list of orders from Cartloom within a date range Classification: read. - Get Order by Email (
get_orders_by_email), Get a list of orders for an email within a date range 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
- Cartloom Domain Required
- API Key Required · protected credential
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Get Products | Yes | No | Get a list of products from Cartloom |
| Get Order | Yes | No | Get an order from Cartloom |
| Create Discount | Yes | No | Create a discount in Cartloom |
| Get Discount | Yes | No | Get discount info from Cartloom |
| Get All Discounts | Yes | No | Get a list of discounts from Cartloom |
| Get Order by Date | Yes | No | Get a list of orders from Cartloom within a date range |
| Get Order by Email | Yes | No | Get a list of orders for an email within a date range |
| Custom API Call | Yes | No | Make a custom API call to a specific endpoint |
Supported actions
Get Products · Read
Get a list of products from Cartloom
get_products · Risk: low · Retry: safe
Get Order · Read
Get an order from Cartloom
get_order · Risk: low · Retry: safe
Inputs
invoice· string · Required, The invoice ID for the order you want to retrieve
Create Discount · Read
Create a discount in Cartloom
create_discount · Risk: low · Retry: safe
Inputs
title· string · Required, Enter the title of the discountenabled· boolean · Required, Is this discount enabled?auto· boolean · Required, Is this discount automatically applied?unlimited· boolean · Required, Is this discount unlimited?selfDestruct· boolean · Required, Remove the discount after useapplyOnce· boolean · Required, Apply the discount once per ordertype· string · Required, Select the type of discountamount· number · Required, Enter the amount of the discounttarget· string · Required, Select the target of the discountstartDate· string · Required, The start date of the discount. YYYY-MM-DD HH:MM:SSstopDate· string · Required, The stop date of the discount. YYYY-MM-DD HH:MM:SSoptional· string · Optional, ## Optional Settings based on above settingscode· string · Optional, Enter the discount code. Leave blank for no code.targetPids· array · Optional, Select the products to apply the discount totargetAmount· number · Optional, The target amount for the discount when the target is set to TotaltargetQuantity· number · Optional, The target quantity for the discount when the target is set to All or Productsallowance· number · Optional, The number of times the discount can be used
Get Discount · Read
Get discount info from Cartloom
get_discount · Risk: low · Retry: safe
Inputs
discountId· string · Required, Enter the ID of the discount you want to retrieve
Get All Discounts · Read
Get a list of discounts from Cartloom
get_all_discounts · Risk: low · Retry: safe
Get Order by Date · Read
Get a list of orders from Cartloom within a date range
get_orders_by_date · Risk: low · Retry: safe
Inputs
start· string · Required, Select a date to start the searchend· string · Optional, Select a date to end the search. Defaults to today.
Get Order by Email · Read
Get a list of orders for an email within a date range
get_orders_by_email · Risk: low · Retry: safe
Inputs
start· string · Required, Select a date to start the searchend· string · Optional, Select a date to end the search. Defaults to today.email· string · Required, Email address to search for.
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 Cartloom 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:
- Cartloom Domain (
domain), required. - API Key (
apiKey), 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-cartloom@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 8 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 Cartloom 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-cartloom@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.