Use this board to submit feature requests, upvote and report bugs.
Share your product feedback!
Export LinkedIn conversations and access them via API (full message text)
What you'd be able to do Get a complete record of your LinkedIn conversations outside of Sendr: every message you send and every reply your prospect sends, with full text and timestamps. You could retrieve full threads through the API, export them from the Unibox, or receive each message as a webhook event as it happens (message sent, and every reply received, not just the first). Why it helps Regulated businesses (for example, FINRA-registered firms) must keep an archive of all client and prospect communications. Without a way to get conversations out of Sendr, they can't use LinkedIn outreach while staying compliant. It also helps teams that want to sync full conversation history into a CRM or data warehouse.
Add custom tracking codes (Google Analytics, Meta Pixel) to personalised pages
What you'd be able to do Add your own tracking scripts, such as Google Analytics, Google Tag Manager or a Meta Pixel, to Sendr personalised pages, so visits and conversions show up in your own analytics and ad platforms alongside Sendr's built-in engagement tracking. Why it helps Teams that already measure their funnel in GA or run retargeting through Meta want Sendr page traffic in the same place, without relying only on Sendr's engagement events or wiring up webhooks. Current state Sendr pages track page views, video and audio plays, button clicks and meetings booked automatically, and these can be pushed out via webhooks. Custom head scripts or pixels can't be added today. Source Raised by a customer via Fibi support chat on 14 Oct 2026.
Manual "Run now" trigger to start a sequence on selected contacts
What you'd be able to do Start a sequence on demand with a manual "Run now" trigger: select specific contacts in a sheet and push them through the sequence immediately with one click, the way tools like n8n, Zapier and Pabbly offer a manual trigger. Why it helps Sometimes you only want to run a flow (for example find phone and email, then send) for a handful of hand-picked contacts, without setting up a schedule, webhook or engagement trigger. Today Available triggers are Schedule, Contact engages with page, Webhook and Row added to sheet. There is no manual or on-demand trigger. Raised by a customer via support chat. Related: "Test a sequence with sample contact data before going live".
Support AND / OR logic within a single Condition step in the Sequencer
What you'd be able to do Combine multiple rules inside one Condition step using AND / OR (for example: "Find Phone is not empty AND Job Title contains Founder", or "Replied OR Page viewed"), the way tools like n8n, Zapier and Pabbly allow. Why it helps Branching on more than one signal currently means chaining several Condition steps or wiring branches together, which makes sequences harder to build and read. Today A Condition step evaluates a single comparison (left operand, comparator, right operand). AND requires chaining two Condition steps; OR requires routing multiple branches to the same next step. Raised by a customer via support chat.
Auto-scrape leads from future LinkedIn posts
Automatically scrape leads from all future LinkedIn posts without requiring a URL to be added manually for each post. Currently each LinkedIn post must be added to a campaign by hand, which does not scale for ongoing posting. The feature should keep campaigns continuously fed with leads from reactions and comments on new posts.
Lead Finder: save company lists and use them to filter People search
What you'd be able to do Search for companies in Lead Finder using company-level filters Save the companies you want to a named account list In People search, filter to only people who work at companies on that list (for example, data scientists and data engineers at these 10 accounts only) Why it helps Account-based teams start from a target account list, then find the right people inside those accounts. Saved company lists make that a two-step workflow inside Sendr. Today Lead Finder is people-first. You can search by company names, but there's no way to save a list of companies and reuse it as a filter in People search.
Rejected
Sync Sendr outreach activity to HubSpot contact and company timelines
What you'd be able to do Have every email, LinkedIn message and WhatsApp message Sendr sends (and every reply received) automatically logged on the matching contact's activity timeline in HubSpot, linked to the right contact and company records. Why it helps Teams that report on pipeline and account engagement in HubSpot need it to reflect outreach run from Sendr, with no manual logging. This also enables account-level reporting, for example seeing which companies within a parent group have been engaged. Today HubSpot can trigger Sendr campaigns via the Automation Builder, but Sendr activity isn't automatically written back to HubSpot contact records.
Planned
Scoped API keys (read-only, write, per-channel permissions)
What you'd be able to do Set scopes when creating an API key: read-only, write, or full access, with per-area toggles (for example, allow LinkedIn and email sending but not WhatsApp). Why it helps Limits exposure if a key is shared with an automation or third-party tool, so each integration only gets the access it needs. Today Creating an API key gives full access with no scope options.
Withdraw pending LinkedIn connection requests (sequence step + bulk withdraw)
What you'd be able to do Add a Withdraw Connection step anywhere in a LinkedIn sequence See all pending connection requests per LinkedIn seat, alongside LinkedIn's limits Withdraw pending requests individually or in bulk Why it helps Pending invites pile up and count against LinkedIn's limits, which puts accounts at risk. Today that means a weekly manual clean-up inside LinkedIn. Today The Send Connection and Wait step can auto-withdraw a request after a set number of days, but there's no standalone withdraw step and no view of pending invites per seat.
Change "Preparing Your Video" to "Loading Your Video"
Replace the "Preparing Your Video" placeholder with "Loading Your Video" on the personalized video page. The current wording implies the video has not been made yet, which contradicts the email copy telling the lead the video is ready. Leads who reach the page before generation finishes see a message that misrepresents the state.
Add image in the email signature
Add support for configuring an email signature that includes an image. Currently, signatures with images are not supported.
Connect any email inbox via SMTP
Connect an email inbox from any provider that supports SMTP as a sending channel, not just Gmail and Outlook. Why it helps Many teams send from mailboxes hosted by their web host or a smaller email provider. SMTP support would let them run Sendr sequences from those inboxes without moving to Google Workspace or Microsoft 365.
Warn when an enrichment has already been run on a table recently
When you trigger an enrichment on a table where that same enrichment already ran in the last 7 days, Sendr currently does nothing and gives no feedback. It can look like the action failed or was ignored. The request: Show a clear notification when an enrichment was already run recently, including when it last ran, so you can decide whether to skip or re-run it. This saves credits and removes the guesswork.
Send now option for testing sequences, Show the scheduled send time on the canvas, 15m options.
Schedules and paced sending protect your inbox reputation when sending to real lists, but during setup they mostly slow you down. Waiting for the next slot, then for the send to go out, can turn a quick test into a long wait. Related improvements Show the scheduled send time on the canvas. Once you set a time on a step and close the panel, it isn't visible anywhere on the canvas. Showing it on the step card would make it easy to see at a glance when each step will fire. 15m options. The time picker currently offers 30m slots. Shorter slots would reduce the wait when testing.
Send outreach steps at the right time in each prospect's timezone
Right now, campaigns apply a single timezone to all sends. If your sending window is set to 9am East Coast time, a prospect in San Francisco gets your connection request at 6am their time, which hurts acceptance rates. It would be great if Sendr could automatically detect each prospect's local timezone (based on their LinkedIn location) and schedule each outreach step to fire at the configured time in their timezone, not yours. This would mean every prospect gets your message at a sensible hour for them, regardless of where they are in the world, with a fallback to the campaign timezone when their location cannot be determined.
Save and reuse variable mapping for Personalised Pages
Re-entering the same mapping each time is repetitive and makes it easy to slip up (for example, putting a full name where only a first name belongs). A saved mapping you can see and edit saves time and makes it easy to check and correct what's mapped before pages are created.
Support for custom / bring-your-own proxies on LinkedIn channels
Allow customers to assign their own custom proxy (IP) to each connected LinkedIn account, the way GetSales and similar LinkedIn automation tools do today. Why it matters: customers running multiple LinkedIn accounts (e.g. "mirror" profiles for outreach at scale) need each account to keep a consistent, distinct IP so LinkedIn doesn't flag multiple accounts as linked to the same operator. Sendr's LinkedIn connection flow (Settings > Channels > Add channel > LinkedIn) is a standard OAuth-style authorization with no field for entering a proxy, and all LinkedIn actions run through Sendr's Unipile-backed cloud automation with no customer-facing IP/proxy control. Customer context: Tony (Talent Architects) currently uses GetSales for his mirror-profile accounts specifically because it supports custom proxies, and asked whether Sendr offers an equivalent before switching outreach tools for those accounts.
MCP
Hi Team, MCP is becoming a standard feature across most tools now. If you can create an MCP connection and made it available to all accounts, I would for sure use Sendr more often. Thanks
Upload a sales PDF or deck to auto-generate a campaign
It would be great to be able to upload a sales deck or PDF directly into Campaign Co-Pilot and have Sendr read it, work out the ideal audience, and automatically generate a campaign based on the content. No more starting from scratch: just drop in your existing collateral and let Sendr do the heavy lifting. As a bonus, it would be useful if the uploaded file could also be offered as an attachment in a follow-up step within the sequence, sent automatically to prospects who respond positively and ask for more information. This would make Sendr incredibly easy to demo and onboard with: hand someone a flyer at an event, upload the PDF, and walk away with a live campaign.
Outbound webhook event for LinkedIn connection requests (sent/accepted)
Add a webhook event category for LinkedIn connection actions in the Sequencer, so customers can route this data to external tools (CRMs like GoHighLevel, Zapier/Make, etc.) the same way page/sheet events already work. Requested events: - connection_request:sent — fires when a Send Connection step sends a request to a contact - connection_request:accepted / connection_request:declined — fires on the existing internal Unipile-backed acceptance signal (already used internally to advance sequences, but not currently exposed as a subscribable outbound event) Customer context: a user wanted to push "people I sent a LinkedIn connection request to" from Sendr into GoHighLevel via a webhook, to trigger their own GHL automation. Today this isn't possible — Sendr's outbound webhook catalogue only covers page render, page engagement, template, and sheet events (see Webhook Events Reference). The connection-accept/decline signal exists internally (Send Connection step listens for a Unipile webhook to advance the sequence) but is not exposed externally. Related existing requests: "Subscribe to reply notifications via webhooks" and "Wait for connection acceptance in sequences, with automatic accepted/not-accepted branching" reflect the same underlying gap (LinkedIn/sequence events not exposed as webhooks).