Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Buffer

Schedule, publish and analyze social media posts across multiple channels with Buffer.

CategoryMarketing
Authenticationcustom
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Buffer

This CDK catalogue package is pinned to @activepieces/piece-buffer@0.1.0 and declares 3 declared actions and 3 declared triggers. Its definition is derived from the exact reviewed Activepieces source.

Provider runtime verification is recorded separately when an approved test connection is exercised; this catalogue entry does not claim that verification.

Technical guide

Technical reference

  • Package: @activepieces/piece-buffer@0.1.0
  • Exact artifact digest: sha256:8f1fca84bea877aa7c0b7ea0ab420f5437e8b9d1308591b13d1faee1949718b6
  • Source: the exact reviewed Activepieces source
  • Authentication, action and trigger schemas are taken from the exact pinned package.

Capability summary

Authenticationcustom
Supported objects6
Supported actionsNot published
Triggers3

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Access Token Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Post Yes No
Create Idea Yes No
Custom API Call Yes No
New Channel Yes No Trigger contract validated offline; live event delivery is tracked separately.
New Queue Item Yes No Trigger contract validated offline; live event delivery is tracked separately.
New Sent Post Yes No Trigger contract validated offline; live event delivery is tracked separately.

Triggers

New Channel · Poll

Triggers when a new channel is connected to your Buffer organization.

Inputs

  • organizationId · string
New Queue Item · Poll

Triggers when a new post is queued in Buffer.

Inputs

  • organizationId · string
  • channelIds · array
New Sent Post · Poll

Triggers when a Buffer post is successfully published.

Inputs

  • organizationId · string
  • channelIds · array

Setup

Setup

Create a tenant connection only in the consuming Studio instance when this connector is made available there. Credentials remain in that tenant's Vault-backed connection and are not stored in CDK package metadata.

Limitations

The package has passed deterministic offline package-load and contract validation. No provider credentials, provider API call or live webhook delivery is represented by this release state.

github.com