Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Queue

A piece that allows you to push items into a queue, providing a way to throttle requests or process data in a First-In-First-Out (FIFO) manner.

CategoryOther
AuthenticationNo authentication required
Version0.1.8
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect Queue with Flows360

A piece that allows you to push items into a queue, providing a way to throttle requests or process data in a First-In-First-Out (FIFO) manner.

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

Available actions

  • Push to Queue
  • Pull items from queue
  • Clear queue

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: Queue
  • Package: @activepieces/piece-queue@0.1.8
  • Exact artifact digest: sha256:98b9fd4fd7a3a9245fd2d83e3c06987ae1dceea2b9c7bf8eb36c655d966db1ac
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

No connection authentication is declared by the package. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Push to Queue (push-to-queue), Push item to queue Classification: read.
  • Pull items from queue (pull-from-queue), Pull items from queue Classification: read.
  • Clear queue (clear-queue), Clears all items inside a queue Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

AuthenticationNo authentication required
Supported objects3
Supported actions3
TriggersNone published

Authentication

Authentication method: No authentication required

Supported objects

ObjectReadWriteNotes
Push to Queue Yes No Push item to queue
Pull items from queue Yes No Pull items from queue
Clear queue Yes No Clears all items inside a queue

Supported actions

Push to Queue · Read

Push item to queue

push_to_queue · Risk: low · Retry: safe

Inputs

  • info · string · Optional, **Note:**n- You can push items from other flows. The queue name should be unique across all flows.n- The testing step work in isolation and doesn't affect the actual queue after publishing.n
  • queueName · string · Required
  • items · array · Required
Pull items from queue · Read

Pull items from queue

pull_from_queue · Risk: low · Retry: safe

Inputs

  • info · string · Optional, **Note:**n- You can pull items from other flows. The queue name should be unique across all flows.n- The testing step work in isolation and doesn't affect the actual queue after publishing.n
  • queueName · string · Required
  • numOfItems · number · Required
Clear queue · Read

Clears all items inside a queue

clear_queue · Risk: low · Retry: safe

Inputs

  • info · string · Optional, **Note:**n- This deletes all items inside the queue permanently.n- The testing step work in isolation and doesn't affect the actual queue after publishing.n
  • queueName · string · Required

Setup

Setup

  1. Add the Queue 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-queue@0.1.8; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 3 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.
  • 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 Queue 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-queue@0.1.8 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