Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Letmepost

Publish and schedule posts to Bluesky, X, LinkedIn, Instagram, Threads, Facebook, Pinterest, and TikTok through one API

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

Overview

Connect Letmepost with Flows360

Publish and schedule posts to Bluesky, X, LinkedIn, Instagram, Threads, Facebook, Pinterest, and TikTok through one API

Use the Letmepost 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 5 actions and 2 triggers.

Available actions

  • Publish a Post
  • Get a Post
  • List Accounts
  • List Media
  • Custom API Call

Available triggers

  • New Published Post
  • Post Event

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: Letmepost
  • Package: @activepieces/piece-letmepost@0.1.0
  • Exact artifact digest: sha256:473dc631c6c021221847dd779825b3f85b8b15906f675d52b9b142a3f2b1e598
  • 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

  • Publish a Post (publish_post), Publish or schedule a post to one or more connected accounts Classification: read.
  • Get a Post (get_post), Retrieve a single post and its per-target results Classification: read.
  • List Accounts (list_accounts), List the social accounts connected to your organization Classification: read.
  • List Media (list_media), List previously uploaded media assets Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Published Post, polling.
  • Post Event, webhook.

Verification

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

Capability summary

Authenticationcustom
Supported objects7
Supported actions5
Triggers2

Authentication

Authentication method: custom

Authentication profiles

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

Supported objects

ObjectReadWriteNotes
Publish a Post Yes No Publish or schedule a post to one or more connected accounts
Get a Post Yes No Retrieve a single post and its per-target results
List Accounts Yes No List the social accounts connected to your organization
List Media Yes No List previously uploaded media assets
Custom API Call Yes No Make a custom API call to a specific endpoint
New Published Post Yes No polling trigger declared by the pinned package.
Post Event Yes No webhook trigger declared by the pinned package.

Supported actions

Publish a Post · Read

Publish or schedule a post to one or more connected accounts

publish_post · Risk: low · Retry: safe

Inputs

  • accounts · array · Required, The connected accounts to publish to
  • text · string · Optional, The post body. Optional when the post is media-only on platforms that allow it.
  • media · array · Optional, Media attachments. Give each item a public URL or an existing letmepost media ID, not both.
  • firstComment · string · Optional, Posted as the first comment under the published post, where the platform supports it.
  • publishNow · boolean · Optional, Publish immediately. Turn off to schedule for a future time.
  • scheduledAt · string · Optional, When to publish the post (ISO 8601). Required when Publish Now is off.
  • profileId · string · Optional, Optional profile to attribute this post to.
  • idempotencyKey · string · Optional, Reusing the same key never publishes twice, which makes retries safe.
Get a Post · Read

Retrieve a single post and its per-target results

get_post · Risk: low · Retry: safe

Inputs

  • postId · string · Required, The ID of the post to retrieve.
List Accounts · Read

List the social accounts connected to your organization

list_accounts · Risk: low · Retry: safe

List Media · Read

List previously uploaded media assets

list_media · Risk: low · Retry: safe

Inputs

  • limit · number · Optional, Maximum number of media assets to return.
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Published Post · Poll

Triggers when a post is published

Post Event · Webhook

Triggers instantly when a post changes state (published, failed, rejected, and more)

Inputs

  • events · array

Setup

Setup

  1. Add the Letmepost 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 (base_url), required.
  • API Key (api_key), 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-letmepost@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 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 Letmepost 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-letmepost@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