Log in to your Marker.io account to give feedback

Feature Requests

Marker.io API
We are considering a Public API for Marker.io that would let teams create, update, and manage issues and projects automatically. With this API, people could connect Marker.io with other tools they already use, making it easier to manage tasks without needing to do everything manually. What the API Could Do: Create and Manage Projects: You could create new projects, get project details, update project info like URLs and guest forms, and even archive old projects when you're done with them. This would save teams a lot of time, especially if they’re working on many projects at once. Manage Issues: You’d be able to pull up issue details and update them from other tools. - This could be helpful if you need to mark an issue as "Resolved" or add comments from your main project management app. It would also allow automatic syncing with systems like Trello or Kanban boards so that when an issue moves to a new stage, it updates in Marker.io too. Update Task Statuses: The API would let you automatically update issue statuses (like Open , Resolved , or Archived ) when changes are made in other tools you use. Right now, webhooks give you some of this, but they only work one way. The API could make this a two-way connection, so things update both in Marker.io and your other apps. Custom Integrations and Automations: The API would allow you to create automatic workflows, like setting up a new project in Marker.io whenever a Slack channel or Trello board is created. It could also help with mobile integrations, so developers can more easily collect issues from different mobile apps without needing extra work from the Marker.io team.
12
Collect Feedback by Email
We’re exploring the idea of letting teams collect feedback by email. Feature Overview Each project could have its own unique email address. When someone sends an email to that address, it could create a new issue in the project. We’re also looking at ways to include useful email details (like attachments or subject lines) to give enough context without extra steps. Use Cases Not everyone wants to use widgets or log into a new tool to share feedback. Some people just prefer email. This idea would make it easy for them to send their thoughts while keeping everything organized in one place. Internal Feedback Teammates who don’t have the widget (e.g., QA, account managers, execs) could simply email the project address. Example: A tester spots a bug on their tablet, sends an email, and the issue appears in the project. Client & External Feedback Agencies could forward client emails directly to the project address instead of retyping them. Or, they could share the project email address with clients , so they can send their feedback straight in. Example: A client’s support agent forwards a checkout bug email to the project address, and it shows up in the backlog. Why This Could Be Useful Keeps all website feedback in one place. No learning curve. Just send an email. Less copy-pasting and manual ticket creation. Works for teammates, clients, and external tools. We’d Love Your Thoughts Please comment below with how you’d use something like this, any specific needs, or examples from your workflow. The more context we have, the better we can deliver it.
0
Load More