Circle.so

What it does

Whenever someone becomes a member of your blog, this plugin asks Circle.so to add that email address to your community, along with their display name if they set one. Give it a space ID as well and the new member is placed in that space right after. Circle is told to skip its own invitation email during the add. If Circle answers that the person is already a member, the plugin counts that as done rather than as an error. The reverse direction covers account deletion: when a member account is removed in VeloCMS, by a GDPR erasure request, an admin delete or the REST API, the plugin asks Circle to drop that email from the community before the record is cleared. Each add attempt is recorded on the Sync activity page of your admin.

Who it's for

Creators who run a blog on VeloCMS and keep the conversation in a Circle.so community, and who want readers who join one to show up in the other without manual invites. You need admin access to Circle to create an API token and read your community ID. It fits best when everyone who joins the blog belongs in the same community, because the plugin does not sort members into different spaces by tier.

How it works

1. 01

   In the plugin settings you enter a Circle API token and the numeric community ID from your Circle admin URL. A space ID is optional.

2. 02

   A reader signs up, buys a membership, or arrives through your admin CSV import. The plugin sends their email and display name to Circle's community members endpoint.

3. 03

   When the community add succeeds and you filled in a space ID, a second request adds the same email to that space. A failure here is logged and nothing more.

4. 04

   The outcome of the community add, success or failure, appears on the Sync activity page, where a failed add can be retried by hand.

5. 05

   When a member account is deleted, the plugin sends a removal request for that email to Circle before VeloCMS clears the record.

Settings you configure

API Token

Created in your Circle community settings under API. It is saved encrypted and sent to Circle as an authorization header on each call.

Community ID

The number that identifies your community, visible in the Circle admin URL. Without it, nothing is sent.

Space ID

Optional. When set, new members are added to this space after joining the community. Leave it empty to add them to the community only.

What it can access

At signup the plugin reads the new member's email address and display name. When an account is about to be deleted, it reads that member's email. Requests go only to app.circle.so, carrying the email, the name and your community and space IDs. It does not touch your posts, orders or newsletter list. Your Circle API token sits in the plugin settings in encrypted form.

Honest limits

• Clicking the newsletter unsubscribe link does not remove anyone from Circle. Removal happens only when the member account itself is deleted.

• Circle's invitation email is switched off for these adds, and VeloCMS does not send one of its own, so tell new members where to find the community.

• Every member goes to the same community and the same optional space. There is no mapping of free or paid tiers to different spaces.

• Members who joined before you set up the plugin are not sent. A full site restore from an export does not send its members either.

• Sync runs one way, from VeloCMS to Circle. People who join or leave inside Circle are not reflected back on your blog.

• A failed space add or a failed removal is only written to the server log. It does not show on the Sync activity page and cannot be retried from there.

• There is no Test connection button. A wrong token or community ID shows up as failed entries on the Sync activity page after the next signup.

Frequently asked questions

Related plugins

• ActiveCampaign
• Pabbly Connect
• Brevo

Specifications

Category

Integrations

Price

Included

Version

1.0.0

Source

First-party