Have something to say?

Bulk visual export of testimonials

Hi Senja team, Is it possible to add a feature in order to bulk visual export of testimonials ? Right now, the only options are: Export all testimonials as a CSV/Excel file (data only) Export each testimonial individually as an image This makes it very time-consuming to create visual content at scale. For example, if I want to publish 10 testimonials on Pinterest, I have to export them one by one. What I'd love to have: The ability to: Choose a visual template/format (dimensions, style) Select multiple testimonials Export all of them at once as individual images in that format. For instance in a single ZIP download This would be a game-changer for anyone using testimonials as social media content, especially on visual platforms like Pinterest, Instagram, or LinkedIn. Thanks for considering it!

Mia about 12 hours ago

πŸ’‘ Feature Request

Discussing

Bulk Edit Testimonials

The ability to select multiple Testimonials, click a button that says "Bulk edit", and edit information about all of them at one time. Context: I'm importing a ton of positive comments from my YouTube videos. I go get the YouTube link, I use the importer via Senja to import the comments, and then I select all the comments I want to import. When I do that, I can easily tag all of them as β€œYouTube”, that's great, but then I have like 40 Testimonials with no star ratings. Before I can approve them, I have to edit each individually and give them all 5-star ratings. Not ideal. A simple solution would be bulk edit, where I could select all of the pieces of Proof that I want and then edit certain fields. You obviously couldn't bulk edit every field, but star ratings, date, source, certain things like that would absolutely be very useful.

Mark 3 months ago

6

πŸ’‘ Feature Request

Discussing

Add programmatic webhook registration API

Automation platforms (Activepieces, Make, n8n, Zapier) need to register and clean up webhooks automatically when a user activates or disables a trigger. This only works if the target app exposes two standard endpoints: POST /v1/webhooks β€” register a URL with a list of events DELETE /v1/webhooks/{id} β€” remove it when the flow is disabled Without these, every user must manually copy a webhook URL from their automation platform and paste it into the Senja dashboard. This is a friction point for non-technical users, and it means orphaned webhooks accumulate in Senja when flows are deleted. This is the standard pattern used by GitHub, Stripe, and Slack. With it, any Senja integration becomes zero-configuration: connect an API key, and webhook lifecycle is handled automatically.

Bastien about 2 months ago

1

πŸ’‘ Feature Request