Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

GhostCMS

Publishing platform for professional bloggers

CategoryMarketing
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect GhostCMS with Flows360

Publishing platform for professional bloggers

Use the GhostCMS 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 6 actions and 6 triggers.

Available actions

  • Create Member
  • Update Member
  • Create Post
  • Find Member
  • Find User
  • Custom API Call

Available triggers

  • Member Added
  • Member Edited
  • Member Deleted
  • Post Published
  • Post Scheduled
  • Page Published

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: GhostCMS
  • Package: @activepieces/piece-ghostcms@0.2.0
  • Exact artifact digest: sha256:ed4ba7b1c3c691efce1b57201d0ddb0c824b1d29d835164ec67c47cae618fdf6
  • 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

  • Create Member (create_member), Create a new member Classification: read.
  • Update Member (update_member), Update a member Classification: read.
  • Create Post (create_post), Create a new post Classification: read.
  • Find Member (find_member), Find a member by email Classification: read.
  • Find User (find_user), Find a staff user by email Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • Member Added, webhook.
  • Member Edited, webhook.
  • Member Deleted, webhook.
  • Post Published, webhook.
  • Post Scheduled, webhook.
  • Page Published, webhook.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects12
Supported actions6
Triggers6

Authentication

Authentication method: custom

Authentication profiles

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

Supported objects

ObjectReadWriteNotes
Create Member Yes No Create a new member
Update Member Yes No Update a member
Create Post Yes No Create a new post
Find Member Yes No Find a member by email
Find User Yes No Find a staff user by email
Custom API Call Yes No Make a custom API call to a specific endpoint
Member Added Yes No webhook trigger declared by the pinned package.
Member Edited Yes No webhook trigger declared by the pinned package.
Member Deleted Yes No webhook trigger declared by the pinned package.
Post Published Yes No webhook trigger declared by the pinned package.
Post Scheduled Yes No webhook trigger declared by the pinned package.
Page Published Yes No webhook trigger declared by the pinned package.

Supported actions

Create Member · Read

Create a new member

create_member · Risk: low · Retry: safe

Inputs

  • email · string · Required
  • name · string · Optional
  • note · string · Optional
  • newsletters · array · Optional
Update Member · Read

Update a member

update_member · Risk: low · Retry: safe

Inputs

  • member · string · Required
  • email · string · Optional
  • name · string · Optional
  • note · string · Optional
  • newsletters · array · Optional
Create Post · Read

Create a new post

create_post · Risk: low · Retry: safe

Inputs

  • title · string · Required
  • slug · string · Optional
  • status · string · Required
  • publishedAt · string · Optional
  • html · string · Required
  • customExcerpt · string · Optional
  • author · string · Required
  • featured · boolean · Optional
  • tags · array · Optional
Find Member · Read

Find a member by email

find_member · Risk: low · Retry: safe

Inputs

  • email · string · Required
Find User · Read

Find a staff user by email

find_user · Risk: low · Retry: safe

Inputs

  • email · string · Required
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

Member Added · Webhook

Triggers when a new member is added

Member Edited · Webhook

Triggers when a member is edited

Member Deleted · Webhook

Triggers when a member is deleted

Post Published · Webhook

Triggers when a post is published

Post Scheduled · Webhook

Triggers when a post is scheduled

Page Published · Webhook

Triggers when a page is published

Setup

Setup

  1. Add the GhostCMS 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:
  • API URL (baseUrl), required.
  • Admin 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-ghostcms@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 6 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 GhostCMS 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-ghostcms@0.2.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