Who moved this?
A customer asks why their request went back to Under review. The log shows who moved it and when.
Private previewWorkspaces are by invitation
Skip to content01Collect
Feedback boardsBoards that ask for exactly what your team needs to act.Votes, comments & mentionsOne vote per person, threads with mentions, and notes only your team sees.In-app widgetFeedback from inside your product, from customers who are already signed in.02Understand
Merge & duplicatesTen posts asking for the same thing become one, with every vote kept.User segments & revenueProSee which requests your biggest customers want, in dollars.InsightsWho reads, what's rising, and whether you answered.HeedPost AIPlus and ProTags, duplicate judging, drafts, summaries, themes and Ask, each with its own switch.03Ship and tell
Roadmap & statusesMove a post and everyone who asked hears, in your own status words.ChangelogRelease notes linked to the requests behind them, mailed to everyone who asked.Notifications & digestThe right email to the right person, and a switch for every one.04Run it
Activity logEvery change, who made it and when, a day at a time.Team, roles & sign-inUnlimited teammates, clear roles, and sign-in your way.Branding, domain & languagesYour logo and colour, your own domain, and 21 languages.ImportMove in from Canny, Featurebase or UserJot, with nobody emailed.05Connect
Slack & issue trackersPlus and ProSlack threads, and issues in Linear, Jira, GitHub or ClickUp that move posts back.MCP serverPlus and ProYour AI agent can read, file, vote and ship, as you.REST APIPlus and Pro27 operations and one key: build anything on top of your feedback.WebhooksPlus and Pro110 events, signed and retried, the moment they happen.Chapter 4 · Run it · Activity log
Every change in HeedPost is recorded as it happens. The activity log shows them a day at a time, grouped by kind of action, and you can narrow it to one person or one day.
Try it
Filter by kind of action or by person. New entries appear at the top as they happen.
Step by step
Admins find it under Insights, in Activity.
The newest changes come first, with a count for each day.
Show one kind of action, one person, or a day picked from the calendar.
Open a person to see everything they did.
The same events can go to your own tools through webhooks.
Who it's for
A customer asks why their request went back to Under review. The log shows who moved it and when.
Filter to People and Configuration: role changes, single sign-on, domains and API keys, each with who did it and when.
Every change is written to the log as it happens, and email, Slack and webhooks follow from that record. Send member, API key and sign-on events to your security tools by webhook.
The details
Newest first, with each day's count and its first few entries, and the rest of the day when you ask. Older days load as you scroll.
Pick one kind of action, one person, or a day on the year calendar. Back returns you to the whole view.
Posts filed and edited, statuses moved, merges, releases published, people invited and removed, settings changed, integrations connected, and what HeedPost did on its own, like the weekly digest.
Who voted, people's own email preferences and reactions stay out, for the same reasons they stay off the board.
The API, the events, and what you can rely on when you build on it.
Every change in HeedPost is written to the log in the same step as the change itself, and live updates, emails and webhooks all follow from that record. Nothing can change without leaving history.
The log can only be added to. The database itself stops anything in it from being edited or deleted.
Each kind of change is either shown in the log or left out by name, and each shows only the details listed for it. When a change gains a new detail, it stays hidden until someone decides it should be shown.
110 event types can reach your webhooks, signed and retried. Slack messages and tracker issues come from the same events.
The log isn't served by the public REST API. Its events reach your webhooks as they happen.
18 event types from this feature reach your webhooks. Each line shows what its data carries.
member.invite_revokedrolemember.invitedrolemember.joinedrolemember.removeduser_id, rolemember.role_changedfrom, toapi_key.createdno extra detailsapi_key.revokedno extra detailssso.configuredno extra detailssso.disabledno extra detailssso.enabledno extra detailssso.rotatedno extra detailswebhook.addedurl, event_typeswebhook.removedurlwebhook.rotatedurlwebhook.updatedurl, wasimport.failedprovider, stateimport.finishedprovider, state, boards, posts, comments, votes, people, user_segments, releases, imagesimport.startedproviderPlans
Free is $0, Plus $29 and Pro $59 a month, per workspace. Never per seat. Every plan, line by line
| Feature | Free | Plus | Pro |
|---|---|---|---|
| Activity log | Included | Included | Included |
| Who can see it | Admins | Admins | Admins |
Something else? Write to us, and a person answers.
No. Changes are added to the log, and nothing in it can be removed.
No. Votes stay out of the log, as they stay off the board.
Yes, through webhooks. You get the same events, signed and retried.
Yes. An API key acts as a person, so its changes carry that person's name.
Yes. Each import appears when it starts, and again when it finishes or fails.
Yes. The Automatic group holds things like the weekly digest.