Circle
Connect Circle posts and comments to your support queue and configure reviewed replies.
Overview
answerLoops receives posts and comments from the Circle spaces you select, prepares replies from workspace knowledge, and runs a separate AI review. Configure automatic replies for the questions that qualify, or review drafts with your team.
Inbound events arrive through Circle Workflows configured by your community administrator.
Setup
1. Create an Admin API token
In Circle, go to Settings → Developers → Tokens, create a new token, and choose type Admin V2. Copy it.
2. Connect in answerLoops
Go to Integrations → Circle and fill in:
| Field | Value |
|---|---|
| Community URL | Your Circle community's base URL, e.g. https://community.example.com |
| Admin API token | The token from step 1 (used to fetch the full post/comment body when a webhook payload is thin) |
| Watched space IDs | Numeric space IDs, comma-separated — leave blank to watch every space |
Click Connect. The card then shows a Webhook URL and a secret token.
3. Create the Circle Workflow
In Circle, go to Settings → Workflows and create a workflow:
- Trigger: New post
- Action: Send webhook
- URL: the Webhook URL from step 2, with
?kind=postappended - Header:
X-AnswerLoops-Token= the secret from step 2 (use the header whenever the Workflow action supports it — if it can't set headers, append&token=<secret>to the URL instead)
- URL: the Webhook URL from step 2, with
Create a second workflow the same way for Trigger: New comment, using ?kind=comment on its URL instead. Circle's webhook payload shape isn't contractual, so kind tells answerLoops which one it's looking at instead of guessing from the payload.
4. Set an escalation user (optional)
Enter the Circle user responsible for follow-up in Escalation user. Escalation routing is included on Pro and Enterprise.
5. Set the confidence threshold
Confidence threshold (0–1, default 0.8) is the score below which the draft is flagged as low-confidence on the ticket.
Environment variables reference
Circle is configured entirely per-organization in the Settings UI. There is no community-wide credential and no environment variable to set. The API token is stored encrypted at rest — set ENCRYPTION_KEY before connecting in any real deployment.