Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Circle

Circle.so is a platform for creating and managing communities.

CategoryOther
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Circle with Flows360

Circle.so is a platform for creating and managing communities.

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

Available actions

  • Create Post
  • Create Comment
  • Add Member to Space
  • Find Member by Email
  • Get Post Details
  • Get Member Details
  • Custom API Call

Available triggers

  • New Post Created
  • New Member Added

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: Circle
  • Package: @activepieces/piece-circle@0.2.0
  • Exact artifact digest: sha256:aaf09c973979175dc91d4955e17adffa99d9508fb5705c267c83394e3d1fd7cd
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. 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 Post (create_post), Creates a new post in a specific space. Classification: read.
  • Create Comment (create_comment), Creates a new comment on a post. Classification: read.
  • Add Member to Space (add_member_to_space), Add an existing member to a specific space by their email. Classification: read.
  • Find Member by Email (find_member_by_email), Finds a community member by their email address. Classification: read.
  • Get Post Details (get_post_details), Retrieves the complete details of a specific post. Classification: read.
  • Get Member Details (get_member_details), Fetches the full profile details for a specific community member. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Post Created, polling.
  • New Member Added, polling.

Verification

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

Capability summary

Authenticationcustom
Supported objects9
Supported actions7
Triggers2

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Token Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Post Yes No Creates a new post in a specific space.
Create Comment Yes No Creates a new comment on a post.
Add Member to Space Yes No Add an existing member to a specific space by their email.
Find Member by Email Yes No Finds a community member by their email address.
Get Post Details Yes No Retrieves the complete details of a specific post.
Get Member Details Yes No Fetches the full profile details for a specific community member.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Post Created Yes No polling trigger declared by the pinned package.
New Member Added Yes No polling trigger declared by the pinned package.

Supported actions

Create Post · Read

Creates a new post in a specific space.

create_post · Risk: low · Retry: safe

Inputs

  • space_id · string · Required
  • name · string · Required, The title of the post.
  • text_body · string · Optional, Simple plain text content for the post. Used if 'Tiptap Body JSON' is not provided.
  • tiptap_body_json · object · Optional, Full TipTap JSON object for the post body. If provided, 'Post Body (Plain Text)' is ignored.
  • status · string · Optional, The status of the post.
  • published_at · string · Optional, If status is 'scheduled', provide the future date and time for publishing.
  • is_comments_enabled · boolean · Optional, Allow comments on this post?
  • skip_notifications · boolean · Optional, Prevent notifications from being sent for this post?
  • user_email · string · Optional, Email of an existing community member to create this post as. If empty, posts as the authenticated admin.
Create Comment · Read

Creates a new comment on a post.

create_comment · Risk: low · Retry: safe

Inputs

  • space_id · string · Required
  • post_id · string · Required
  • body · string · Required, The content of the comment.
  • parent_comment_id · number · Optional, ID of the comment to reply to. Leave empty if not a reply.
  • skip_notifications · boolean · Optional, Skip sending notifications for this comment?
Add Member to Space · Read

Add an existing member to a specific space by their email.

add_member_to_space · Risk: low · Retry: safe

Inputs

  • space_id · string · Required
  • email · string · Required, The email address of the member to add to the space.
Find Member by Email · Read

Finds a community member by their email address.

find_member_by_email · Risk: low · Retry: safe

Inputs

  • email · string · Required, The email address of the member to find.
Get Post Details · Read

Retrieves the complete details of a specific post.

get_post_details · Risk: low · Retry: safe

Inputs

  • space_id · string · Required
  • post_id · string · Required
Get Member Details · Read

Fetches the full profile details for a specific community member.

get_member_details · Risk: low · Retry: safe

Inputs

  • member_id · 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

New Post Created · Poll

Triggers when a new post is created in a specific space.

Inputs

  • space_id · string
New Member Added · Poll

Triggers when a new member is added to the community.

Setup

Setup

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