| name | sales-frill |
| description | Frill (frill.co) platform help — affordable customer-feedback suite (Canny/Nolt/UserVoice alternative): feedback boards (voting/comments), public roadmaps, changelog announcements, surveys, and an embeddable widget. Developer surface: REST API (api.frill.co/v1, Bearer key, cursor pagination via after/endCursor) for ideas/comments/votes/statuses/topics/announcements; HMAC-SHA256-signed webhooks (idea/vote/comment/announcement events; triggered_at/event/data payload); a Frill-Script widget (identify users, surveys); SSO; and 15+ integrations (Slack/Jira/Linear/Intercom/Zapier). Use when reading or syncing ideas/votes via the API, verifying signed webhooks, embedding the widget or identifying users, mapping statuses/topics to your roadmap, or choosing Frill vs Canny/Nolt on price. Do NOT use for voice-of-customer / survey program strategy across tools (use /sales-customer-feedback), feedback aggregation across review/social sources (use /sales-noisely), or generic iPaaS wiring (use /sales-integration). |
| argument-hint | [describe what you need help with in Frill] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","customer-feedback","product","platform"] |
| github | https://github.com/Frill-co |
Frill Platform Help
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
-
What are you trying to do?
- A) Read/sync ideas, votes, comments via the REST API (cursor pagination)
- B) Verify a signed webhook (HMAC-SHA256) and react to idea/vote/comment events
- C) Embed the widget / identify logged-in users / run a survey (Frill-Script)
- D) Map Statuses + Topics to your public roadmap and changelog (Announcements)
- E) Set up SSO or a native integration (Slack/Jira/Linear/Intercom/Zapier)
- F) Decide Frill vs Canny/Nolt (price), or pick a plan
-
API or no-code? Code → REST API + signed webhooks. Front-end → Frill-Script widget. No endpoint → native integrations / Zapier.
Skip-ahead rule: if the user's prompt already provides enough context, skip to Step 2.
Step 2 — Route or answer directly
| If the question is about... | Route to... |
|---|
| Voice-of-customer / survey program strategy (NPS/CSAT) across tools | /sales-customer-feedback {question} |
| Aggregating feedback across reviews/social/support sources | /sales-noisely {question} |
| Connecting Frill to a CRM/PM tool generically (iPaaS) | /sales-integration {question} |
| Public review generation strategy | /sales-customer-reviews {question} |
When routing, give the exact command, e.g. "This is a strategy question — run: /sales-customer-feedback build a closed-loop feedback program".
Step 3 — Frill platform reference
Read references/platform-guide.md for the full reference — the Ideas/Roadmap/Announcements/Surveys module map (what's API vs widget vs UI), the prioritization matrix, plan tiers, the data model, and quick-start recipes (pull ideas via the API; verify a webhook; embed + identify a user).
Read references/frill-api-reference.md for the integration surface — base https://api.frill.co/v1, Bearer API-key auth (from app.frill.co/settings/company), cursor pagination ( ← ), the resources (ideas/comments/votes/statuses/topics/followers/announcements/notes), (events + ///), Frill-Script (widget/surveys/identify), and SSO.
