Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Lightfunnels

Lightfunnels integration for Flows360 workflows.

CategorySales And Crm
AuthenticationOAuth 2.0
Version0.1.7
Published scopes1 published scope
Last updatedSeptember 30, 2026

Overview

Connect Lightfunnels with Flows360

Lightfunnels integration for Flows360 workflows.

Use the Lightfunnels 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 10 actions and 2 triggers.

Available actions

  • List Products
  • Get Product
  • Create Product
  • Get Order
  • List Orders
  • Cancel Order
  • Create Customer
  • Get Customer
  • Plus 2 additional declared actions.

Available triggers

  • New Order
  • New Lead

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: Lightfunnels
  • Package: @activepieces/piece-lightfunnels@0.1.7
  • Exact artifact digest: sha256:21e7fd424a95b7261f4cc5c99fa8b1c003e284bcfc8024aae3b3dbdc3a2c4b88
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

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

Action contracts

  • List Products (list_products), Retrieve a list of all products Classification: read.
  • Get Product (get_product), Retrieve a specific product by ID Classification: read.
  • Create Product (create_product), Create a new product Classification: read.
  • Get Order (get_order), Retrieve a specific order by ID Classification: read.
  • List Orders (list_orders), Retrieve a list of orders Classification: read.
  • Cancel Order (cancel_order), Cancel an order Classification: read.
  • Create Customer (create_customer), Create a new customer Classification: read.
  • Get Customer (get_customer), Retrieve a specific customer by ID Classification: read.
  • List Customers (list_customers), Retrieve a list of customers Classification: read.
  • Get Funnel (get_funnel), Retrieve a specific funnel by ID Classification: read.

Trigger contracts

  • New Order, webhook.
  • New Lead, webhook.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

AuthenticationOAuth 2.0
Supported objects12
Supported actionsNot published
Triggers2

Authentication

Authentication method: OAuth 2.0

Required scopes

products,orders,customers,funnels

Authentication profiles

connection · oauth2

OAuth scopes: products,orders,customers,funnels

Supported objects

ObjectReadWriteNotes
List Products Yes No Retrieve a list of all products
Get Product Yes No Retrieve a specific product by ID
Create Product Yes No Create a new product
Get Order Yes No Retrieve a specific order by ID
List Orders Yes No Retrieve a list of orders
Cancel Order Yes No Cancel an order
Create Customer Yes No Create a new customer
Get Customer Yes No Retrieve a specific customer by ID
List Customers Yes No Retrieve a list of customers
Get Funnel Yes No Retrieve a specific funnel by ID
New Order Yes No webhook trigger declared by the pinned package.
New Lead Yes No webhook trigger declared by the pinned package.

Triggers

New Order · Webhook

Triggers when a new order is created

New Lead · Webhook

Triggers when a new lead subscribes

Setup

Setup

  1. Add the Lightfunnels 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.

OAuth scopes

  • products,orders,customers,funnels
  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-lightfunnels@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 10 actions and 2 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.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Lightfunnels 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-lightfunnels@0.1.7 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