Integrations overview
PushFeedback stores feedback in your dashboard first. On eligible paid plans, you can then send each matching submission to a connected tool without making feedback collection depend on that tool.
Choose an integration
| Need | Integration |
|---|---|
| Create work for a product or support team | Asana, Linear, monday.com, Trello, GitHub Issues, or GitLab Issues |
| Notify a channel | Slack, Microsoft Teams, or email |
| Send a structured event to your own service | Webhooks |
| Create Jira issues through an incoming webhook | Jira Automation |
| Connect an automation platform | Make or Zapier |
Configure any integration
- Open your project in the PushFeedback dashboard.
- Open Settings and select an integration.
- 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 and task 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 }}
Use the editor's variable buttons when available. Static text stays yours. Feedback values are formatted safely for each destination. 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 and is hidden on smaller screens to keep the configuration focused. 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.