Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Hootsuite

Social media management, schedule posts and manage multiple networks from one dashboard.

CategoryMarketing
AuthenticationOAuth 2.0
Version0.1.0
Published scopes2 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Hootsuite with Flows360

Social media management, schedule posts and manage multiple networks from one dashboard.

Use the Hootsuite 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 4 actions and 2 triggers.

Available actions

  • Schedule Post
  • Get Post Details
  • Delete Post
  • Custom API Call

Available triggers

  • New Scheduled Post
  • New Published Post

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: Hootsuite
  • Package: @activepieces/piece-hootsuite@0.1.0
  • Exact artifact digest: sha256:5dda8b788c5dd4727531eb0788e838d901bb31158438bed550b6f76c1a4f3baf
  • 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

  • Schedule Post (create_message), Schedules or immediately publishes a post to one or more social media profiles. Classification: read.
  • Get Post Details (get_message), Retrieves the details of a specific scheduled or published post by its ID. Classification: read.
  • Delete Post (delete_message), Permanently deletes a post. Only posts in a deletable state (e.g. SCHEDULED) can be removed. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Scheduled Post, polling.
  • New Published Post, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

AuthenticationOAuth 2.0
Supported objects6
Supported actionsNot published
Triggers2

Authentication

Authentication method: OAuth 2.0

Required scopes

offlinepost

Authentication profiles

connection · oauth2

OAuth scopes: offline, post

Supported objects

ObjectReadWriteNotes
Schedule Post Yes No Schedules or immediately publishes a post to one or more social media profiles.
Get Post Details Yes No Retrieves the details of a specific scheduled or published post by its ID.
Delete Post Yes No Permanently deletes a post. Only posts in a deletable state (e.g. SCHEDULED) can be removed.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Scheduled Post Yes No polling trigger declared by the pinned package.
New Published Post Yes No polling trigger declared by the pinned package.

Triggers

New Scheduled Post · Poll

Triggers when a new post is scheduled in Hootsuite.

New Published Post · Poll

Triggers when a post is published (sent) in Hootsuite.

Setup

Setup

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

  • offline
  • post
  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-hootsuite@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 4 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.
  • 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 Hootsuite 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-hootsuite@0.1.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.

github.com