FlowRunner
PricingContact
Theme
Start Free

Circle

Social Media

Run your Circle community from your flows. Agents create and update members from CRM or checkout events, cross-post announcements into spaces, apply member tags for segmentation, send invitations, publish events, and revoke access when subscriptions lapse.

22 actions API key available
Circle website ↗ Platform Documentation ↗ Capability data verified 2026-07-27
A subscription payment succeeds for a new customer in billing
Get Community Member checks by email whether this person already has access
Create Community Member adds the new customer, with the invitation email carrying Circle's onboarding link
Tag Member applies the plan-tier tag so gated spaces and segments resolve correctly
Agent confirms the member landed with access to the spaces their tier includes
A community manager reviews the weekly lapse list before any access is revoked, because a failed card is not a decision to leave
The onboarding summary posts with new members, applied tags, and held offboardings

What This Integration Enables

A paid community is an access-control problem wearing a social interface. Who gets in, which spaces they see, and when access ends are all downstream of systems Circle cannot see: billing, CRM, course platforms. This connector gives FlowRunner agents the admin keys: they create and update members from checkout and CRM events, apply and remove member tags for segmentation, cross-post announcements and publish events into spaces, send invitations, and revoke access when a person actually leaves. The operating principle: joining should be instant and leaving should be deliberate. Agents handle the instant half without help; the deliberate half gets a human. - Onboard paying customers as members the minute payment clears - Tag members into plan tiers and behavioral segments automatically - Cross-post announcements into spaces with HTML formatting - Publish events with ISO 8601 schedules and pull RSVP details outward - Queue lapse-driven offboarding for human review before access is revoked

Without FlowRunner

Membership lags billing Paid customers wait days for access while cancelled ones keep it for months
Announcements live in one channel News posts to email or Slack but never reaches the community space, or vice versa
Segments are static Member tags reflect whoever ran the last manual cleanup, not current plan or behavior

With FlowRunner

Access tracks the subscription Payment events create members and tag tiers within minutes, and lapses queue for human review
Announcements fan out One flow cross-posts to the right space with formatting intact and the discussion tracked
Segments update themselves Tags apply and remove as plans change in billing and activity changes in the stack

Use Case Scenarios

Checkout to community in one motion

A payment confirms in [Stripe](/integrations/stripe). The agent calls Create Community Member with the customer's email and display name, letting Circle's invitation email deliver the onboarding link, then Tag Member with the tier tag resolved from List Member Tags. The customer posts their introduction the same afternoon they paid, and the community manager never touches a spreadsheet of pending adds.

The announcement that reaches everywhere

Product marketing finalizes a launch note. The agent resolves the announcements space with List Spaces, calls Create Post with the HTML body as a draft, and pings the community manager to review before publishing. Once live, the post URL fans out: [Gmail](/integrations/gmail) for the email list, [Slack](/integrations/slack) for the internal team. Comments accumulating on the post get pulled by List Comments into the feedback digest, so the community's reaction reaches the people who shipped the thing.

Events synced out, RSVPs synced in

The team schedules a monthly workshop with Create Event in the events space, ISO 8601 timestamps and location set. The agent emails members the RSVP link and logs the event to [Google Sheets](/integrations/google-sheets). As the date approaches, Get Event pulls attendee counts into the prep channel, so the host knows whether to book the big Zoom or the small one. After the event, attendance data joins the engagement picture that drives tag-based segmentation.

Human-in-Loop Highlight

Delete Community Member is permanent: it revokes all access and cannot be undone, and in a community the record it destroys is not just an account but a person's post history, course progress, and standing. The tempting automation is wiring it straight to billing, subscription lapsed, member deleted, and that automation deletes a founding member the week their corporate card rotates. So FlowRunner offboarding flows stage every deletion. The agent assembles the docket from Get Community Member and the billing context: "Subscription lapsed 14 days ago, two payment retries failed, member since 2024, 212 posts, moderator of the Founders space. Revoke?" The community manager decides, and often the answer is a dunning email instead of a deletion. Access ends when a person confirms the relationship has, not when a card expires.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via email
Human decides
Agent resumes with decision

Agent Capabilities

22 actions

Members

5
  • List Community Members Lists members with pagination, optionally filtered to those with access to a specific space. Returns id, name, email, headline, and access details.
  • Get Community Member Retrieves one member by ID or email with full profile and access details. The check that fronts onboarding and offboarding decisions.
  • Create Community Member Adds a member by email, optionally setting display name and skipping the invitation email. The instant half of access control.
  • Update Community Member Updates a member's name, headline, or bio by member ID, changing only supplied fields.
  • Delete Community Member Removes a member entirely and revokes all access, permanently. Gated behind human review in every FlowRunner offboarding flow.

Spaces

4
  • List Spaces Lists the community's spaces, feeds, discussions, courses, events, with id, name, slug, type, and parent group.
  • Get Space Retrieves one space with name, slug, type, privacy setting, and space group.
  • List Space Groups Lists the top-level sidebar containers that organize spaces, with settings.
  • Get Space Group Retrieves one space group with name, slug, and navigation and visibility settings.

Posts

3
  • List Posts Lists a space's posts with pagination and sorting: title, body, author, engagement counts, timestamps.
  • Get Post Retrieves one post in full, including body content and engagement counts.
  • Create Post Creates a post in a space with a title and HTML body, published immediately or saved as a draft. Draft-first is how FlowRunner flows keep a human on the publish button.

Comments

2
  • List Comments Lists a post's comments with author, body, parent comment for replies, and timestamps. The read behind feedback digests.
  • Create Comment Adds a comment to a post, optionally as a reply, with HTML formatting.

Events

3
  • List Events Lists events community-wide or per hosting space, with schedules, location, and RSVP details.
  • Get Event Retrieves one event with full details and attendee and RSVP information.
  • Create Event Creates an event in an events-type space with name, description, ISO 8601 start and end times, and location type.

Tags

3
  • List Member Tags Lists the community's member tags with id, name, color, and display settings. The segment vocabulary.
  • Tag Member Applies a tag to a member by member ID and tag ID, adding them to the segment.
  • Untag Member Removes a tag from a member without deleting the tag itself.

Invitations

1
  • Create Invitation Creates and sends an invitation email with a join link, optionally personalized. The onboarding path when membership precedes account creation.

Communities

1
  • List Communities Lists the communities the API token can reach, confirming the community ID and settings the token operates on.

Frequently Asked Questions

What can FlowRunner do with Circle?

FlowRunner agents can run List Community Members, Get Community Member, and Create Community Member in Circle, plus 19 more actions.

Does connecting Circle to FlowRunner require OAuth?

No. Circle connects to FlowRunner with an API key, no OAuth flow required.

Can Circle trigger a FlowRunner workflow automatically?

Circle doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Circle

$100 in credits. No card required. Connect in minutes.