Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Webling

Webling integration for Flows360 workflows.

CategoryProductivity
Authenticationcustom
Version0.1.6
Published scopes0 published scopes
Last updatedOctober 6, 2026

Overview

Connect Webling with Flows360

Webling integration for Flows360 workflows.

Use the Webling 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 1 action and 2 triggers.

Available actions

  • Get Events by ID

Available triggers

  • New or Updated Event
  • On Changed Data

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: Webling
  • Package: @activepieces/piece-webling@0.1.6
  • Exact artifact digest: sha256:3205046e729087b99da6b80c517fd91f42ffb6f324940aa2c180cd928388d35f
  • 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 Events by ID (EventsById), Gets event data by a list of event IDs and optional calendar ID to filter. Classification: read.

Trigger contracts

  • New or Updated Event, polling.
  • On Changed Data, polling.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects3
Supported actions1
Triggers2

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Base URL Required
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Get Events by ID Yes No Gets event data by a list of event IDs and optional calendar ID to filter.
New or Updated Event Yes No polling trigger declared by the pinned package.
On Changed Data Yes No polling trigger declared by the pinned package.

Supported actions

Get Events by ID · Read

Gets event data by a list of event IDs and optional calendar ID to filter.

events_by_id · Risk: low · Retry: safe

Inputs

  • eventIds · string · Required, Comma separated list of event IDs (e.g. '536,525,506,535'). When at least one ID doesn't exist the whole query return a 404 error.
  • calendarId · string · Optional, Calendar to filter the events by.

Triggers

New or Updated Event · Poll

Triggers when an event is added or updated.

Inputs

  • calendarId · string
On Changed Data · Poll

Triggers when anything was added, updated or deleted since last request.

Setup

Setup

  1. Add the Webling 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:
  • Base URL (baseUrl), required.
  • API Key (apikey), 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-webling@0.1.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 1 action 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 Webling 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-webling@0.1.6 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