Integrations overview
PushFeedback stores feedback in your dashboard first. Connect an integration to send matching submissions to another tool. A delivery failure does not remove the feedback from PushFeedback.
Choose an integration
| Need | Integration |
|---|---|
| Read and manage feedback from an AI assistant | MCP server |
| Create issues, tasks, or cards | Jira Automation, Linear, GitHub Issues, GitLab Issues, Asana, monday.com, or Trello |
| Notify a channel | Slack, Microsoft Teams, or email |
| Connect custom or automated workflows | Webhooks, Make, or Zapier |
Configure any integration
- Open your project in the PushFeedback dashboard.
- As a team Administrator, open Settings, then select a card under Integrations.
- Add its destination and credentials.
- On wider screens, review the live preview while you edit.
- Save the integration and use Test connection where available before relying on live feedback.
Issue tracker and management tool integrations, channel integrations, and webhook-based automation are available on the Professional and Unlimited plans. Email notifications are available on every plan.
Delivery behavior
Enabled integrations send feedback matching their delivery controls and rules to the configured destination. Use Test connection after changing credentials or a destination.
Build the message your team needs
Several integrations let you configure a title and body with variables such as:
{{ feedback.message }}
{{ feedback.rating_label }}
{{ feedback.url }}
{{ feedback.detail_url }}
{{ project.name }}
See message templates and delivery rules for all variables, filters, and JSON examples. Use the editor's variable buttons when available. Webhook, Slack, Linear, Trello, and monday.com also support their documented delivery rules or field mappings.
Preview and connection tests
A live preview shows how the project's latest feedback will appear at the destination while you edit. If the project has no feedback yet, the editor uses sample data. The preview is available on wider screens. Previewing does not save a draft or create a task, issue, card, or board item.
Connection tests verify the configured destination. Webhook, Slack, and Teams tests send a small test payload. Issue and task integrations validate access and the selected destination without creating work in that provider. Jira Automation is tested by submitting feedback after the Jira rule and PushFeedback connection are saved.
Troubleshooting delivery
- Confirm the response exists in your PushFeedback project.
- Check Enabled, Require a message, and any delivery rules.
- Check the destination and credentials, then run Test connection where available.
- Submit a new response that matches the rules and check the destination. A connection test does not prove that a full feedback delivery works.
If a saved secret needs replacing, paste the new value and save. A blank secret field keeps the existing credential where the editor offers that behavior.