FeedbackPulse Integrations
FeedbackPulse integrations help your team connect feedback data with the tools you already use. Today, FeedbackPulse supports Slack survey messages and AI assistant access through MCP. Native API support is being prepared for a future release, and additional automation options are under consideration.
What to read first
Section titled “What to read first”| Goal | Start here |
|---|---|
| Send survey invitations and reminders in Slack | Connect Slack to FeedbackPulse |
| Connect an AI assistant to FeedbackPulse | FeedbackPulse MCP Overview |
| Manage MCP access and personal tokens | Manage FeedbackPulse API Tokens |
| Connect Claude Desktop | Connect Claude Desktop to FeedbackPulse |
| Connect Claude.ai | Connect Claude.ai to FeedbackPulse |
| Connect Claude Code or another token-based client | Connect Claude Code to FeedbackPulse |
| Review supported MCP tools and prompts | FeedbackPulse MCP Tools Reference |
| Fix connection, token, or permission errors | Troubleshoot FeedbackPulse MCP Connection |
Slack survey messages
Section titled “Slack survey messages”FeedbackPulse can send survey invitations and reminders as Slack direct messages alongside email. This helps employees notice surveys in the place they already work, while keeping email delivery in place as the fallback channel.
Start with Connect Slack to FeedbackPulse to connect your Slack workspace and choose when Slack direct messages should be sent.
AI assistants and MCP
Section titled “AI assistants and MCP”FeedbackPulse uses the Model Context Protocol (MCP) to let approved AI assistants answer questions about surveys, review cycles, recognition, employees, and supported template workflows.
MCP access must be enabled for your organisation by an Admin. Admins always have MCP access automatically. Non-admin users need an Admin to grant them access before they can connect an assistant, and only Admins can create personal API tokens (for themselves).
Native API support
Section titled “Native API support”Native API support is being prepared for the next release cycle. Once the production release is available, this section will link to the full API setup and reference documentation.
Until then, use the MCP guides above for supported AI assistant connections. MCP API tokens are for assistant and MCP client access; they may not cover every native API workflow.
Automation tools
Section titled “Automation tools”FeedbackPulse is exploring additional automation options, potentially including Zapier-style workflows, for a future release. This is a roadmap idea, not a scheduled feature, and no release date is set. Dedicated setup guides will be added here if and when a production automation flow becomes available.
For now, contact support@feedbackpulse.com if you need help preparing an integration workflow.