Workspace API keys introduced programmatic LinkedIn account discovery, lead-backed outreach enrollment and enrollment status. Public API documentation and identity validation made the contract usable by external integrations.
How to use it +
Open Workspace → API keys, create a key and follow the API documentation for account discovery and outreach enrollment. Store the generated key securely.
Continue a connection conversation with timed follow-ups after acceptance, using a saved playbook.
How to use it +
Open a connect playbook in Playbooks.
Configure the invitation and enable the first follow-up after acceptance.
Add the message and set its delay.
Enable later follow-ups in order, with their own messages and delays.
Save the playbook and select it for outreach.
The playbooks and follow-ups guide explains the current editor, step dependencies and reply behavior. It is shared with the playbook feature so there is one maintained setup source.
Matrix searches combine multiple keywords and locations into a grouped run, with aggregate progress and individual scan details. Controls and grouped history were refined after the first implementation.
How to use it +
In the lead search builder, use the matrix search controls, add keywords and locations, then review the matrix preview before starting.
Comment runs gained personal and company identity selection, live progress, run controls and more reliable result reporting. Comments history distinguishes scanned, evaluated, skipped, failed and posted work.
How to use it +
Open Comments, start a one-off run, choose the available commenting identity and inspect the run details as it progresses.
The early Free-plan default daily AI allowance increased from 10 to 20 calls, while preserving higher operator-configured allowances. This is a historical allowance change, not the current pricing contract.
How to use it +
No setup was needed for the implementation. Check Billing for the current plan and allowances.
Inbox read paths, local thread selection and stale-request handling were improved. History catch-up avoids duplicate scans, reports terminal outcomes and blocks conversations that cannot accept messages.
How to use it +
Use Inbox normally. Import from messages in Leads or the inbox history controls when you need to synchronize conversations.
Relinta added account-scoped views and preferences, so lead relationships, inbox activity and automation settings can follow the selected LinkedIn profile. Later fixes keep surfaces synchronized when the account changes.
How to use it +
Use the LinkedIn account selector in the app header. Open an account in LinkedIn accounts to manage its settings.
Recurring comment automation added a schedule, identity choice and run settings. This early Auto-comment workflow was later consolidated into the shared campaign system.
How to use it +
For the current workflow, open Campaigns, create a Feed comments campaign and configure identities, topics and its schedule.
People Search gained location lookup for cities, regions and countries, plus saved filter summaries in scan history. LinkedIn geography is normalized for lead locations and country values.
How to use it +
In Leads, open Add leads → Create search in Relinta. Choose locations and review the search filters before starting.
LinkedIn people-search imports, Sales Navigator searches, conversation loading and profile capture became less dependent on the layout of LinkedIn pages.
How to use it +
No setup is needed. Use the regular lead scan and inbox workflows; account access to LinkedIn and Sales Navigator still applies.
The lead table gained column visibility, reordering, saved layout, and reset controls. Structured first and last names improved lead display and connection-note/reply personalization.
How to use it +
In Leads, open Columns to choose visible fields; enable reordering to drag headers. Use Reset columns to restore the default layout.
Lead qualification controls and connection-degree data were restored and normalized, making fit decisions and connection filtering available again in the lead table.
How to use it +
In Leads, review a person’s connection information and use the fit controls to mark them Fit, Not fit, or Unreviewed.
Inbox synchronization was repaired across opened-thread identification, message parsing, event depth, and LinkedIn API retrieval, helping conversations and their messages arrive with the correct identity and context.
How to use it +
Open Inbox and review the synchronized conversations. The synchronization fixes apply automatically.
Self-profile capture and AI-default generation were hardened to preserve useful profile context and reject invalid captures instead of building settings from the wrong or incomplete page.
How to use it +
No setup is needed for capture validation. Review generated context before using it in outreach.
Bulk invitation runs stopped when LinkedIn reported its weekly invitation limit, avoiding repeated attempts against the same limit and showing the stopped state in the run summary.
How to use it +
No setup is needed. Review the bulk invitation run summary when a weekly limit stops a run.
Bulk invitation progress distinguished sent, skipped, and failed outcomes instead of relying on a single aggregate count. Completed summaries stayed visible, and clearer run-status handling explained partial results.
How to use it +
Open the bulk invitation run summary to review its outcome breakdown after the run finishes.
An early daily auto-outreach setting reused a saved lead filter and the bulk invitation workflow, with a visible enabled state and last-run information.
How to use it +
Historical automation: this daily Auto-outreach drawer is retired. Configure current recurring outreach through Campaigns.
A connection invitation could use a one-off edited note instead of sending the saved template unchanged. Later refinement preserved the draft while account and template data loaded.
How to use it +
Open a lead’s connection-invite action, edit the final connection note, review it, and send.
Task scheduling and runner-window lifecycle were consolidated, with foreground outreach prioritized and background windows normalized and cleaned up more consistently.
How to use it +
No setup is needed. These fixes apply when browser-backed LinkedIn actions run.
Scan runs gained a detail drawer with progress, retry/cancel actions, and a link to the page that failed. The extension popup launcher and ready-browser checks were rebuilt to use the same run contract.
How to use it +
Open a scan from Leads scan history to inspect its details and, when available, follow the failed-page link.
Live updates began carrying scan counts, new leads, inbox messages, approvals, bulk invitation results, and comment progress into the web app. Reconnection and state handling were hardened to reduce stale or flickering progress.
How to use it +
Keep the relevant run or workspace view open; progress and new activity update automatically.
A setup checklist guided new users through extension installation, connecting the actual LinkedIn account, AI setup, and starting work. Account binding and activation fixes prevented unrelated or dormant installs from falsely completing setup.
How to use it +
Historical checklist: the original extension-first onboarding is superseded. Use the current LinkedIn accounts connection flow in the web app.
The app added a way to request extension updates when a connected browser was running an outdated version, with follow-up work simplifying version refresh and update policy.
How to use it +
No setup is needed for version detection. Follow any update instruction shown for your connected browser.
Background outreach became more resilient to interruptions. Stuck invitations and interrupted actions recover more consistently, helping work continue without restarting the whole run.
How to use it +
No setup is needed. Continue using the normal scan, invitation, and messaging actions; inspect their run status if an action fails.
Sign-out began revoking and clearing the extension session, and installation tokens and tasks were scoped more strictly to the authenticated user and workspace.
How to use it +
Use the web app’s sign-out action when ending your session. No additional setup is needed for the session-isolation fixes.
Inbox synchronization began checking conversation previews before fetching changed threads. Automatic reply scheduling was restored and incoming-message events could trigger reply generation, reducing unnecessary thread work.
How to use it +
No setup is needed for synchronization improvements. Automatic replies depend on your enabled automation settings; the early implementation is not a statement about today’s reply policy.
Registration, heartbeat, production-origin, and account-binding fixes addressed browsers becoming dormant or stale soon after sign-in and extension requests failing before they could run work.
How to use it +
No setup is needed for the fixes. Check the account/browser connection status if LinkedIn actions cannot start.
The saved connection-note template moved from workspace-wide configuration to each user’s profile, allowing different operators to keep their own outreach wording.
How to use it +
Historical configuration: template ownership has since evolved. Review the current note settings in the connection-invite or campaign editor.
Bulk invitations moved into a drawer on Leads and began using the same filters and match count as the table, so the chosen recipients matched the working list.
How to use it +
Filter Leads, open the bulk invitation action, review the recipient scope and note settings, then start the run.
Leads, Inbox, scans, comments, settings, activity, and a workspace overview moved into a web application. The extension became a companion for LinkedIn actions instead of hosting the full workspace.
How to use it +
Sign in to the Relinta web app, then open Leads, Inbox, or Comments from the navigation.
The web Inbox gained generated drafts and approval controls, with reply-send outcomes tracked separately from approval. Connection notes and comments also joined the approval workflow.
How to use it +
Historical approval workflow: review and reply controls now live in the current Inbox and action-specific editors; do not use the retired workflow console.
The extension added feed-commenting runs with a target comment count, relevance scores, start/stop controls, and a history of posted and failed comments.
How to use it +
Historical setup: the original extension Comments page is retired. Current comment workflows are available in Comments in the web app.
Lead filtering moved to server-side queries with accurate match counts and infinite scrolling. Filter persistence and navigation fixes made it easier to return to the same working list without empty-state flashes.
How to use it +
Open Leads, apply the available column filters, and scroll to load more matches. The match count reflects the filtered result set.
The early scan page gained a simpler URL-based composer, reusable presets, page-count controls, and scan-history cards. Preset loading no longer needed a server round trip.
How to use it +
Historical scan page: scanning now lives within Leads. Use the current search or LinkedIn URL scan flow rather than the retired standalone scan route.
Email-code sign-in replaced the earlier magic-link flow. The form gained resend, change-email, and remembered-email behavior, while longer-lived sessions and the web-to-extension bridge reduced repeated authentication. Expired-session responses redirected to sign-in instead of showing an empty workspace.
How to use it +
Enter your work email on Sign in, choose Email me the code, and enter the six-digit code. Use Resend code or Use a different email if needed.
A settings toggle extended automatic approval beyond single-operator connection invites to all approval types, while pending inbox approvals were accounted for in reply state.
How to use it +
Historical setting: this early workspace-wide approval toggle has been superseded by the current action and automation controls.
Lead detail drawers opened without waiting for a full page reload, and a direct connection-invite action used the saved note template and an eligible browser. Outcome events became visible in lead history.
How to use it +
Select a lead in Leads, open the connection-invite action, review the final note, and send when ready.
Messaging insights added inbound-message and unique-lead trends, time grouping, and comparisons with the previous period. A later web update replaced the daily table with an interactive trend chart.
How to use it +
Open Insights to review messaging trends. The original extension chart is historical.
Browser installs were associated with LinkedIn accounts, and workflow targeting gained account context to reduce ambiguity about which account would perform an action.
How to use it +
Open LinkedIn accounts to review connected accounts; use the account selector when launching an account-scoped action.
The web app added workspace membership and plan/AI-quota information, giving operators a place to see their workspace and usage context. This change did not establish a new paid-plan launch.
How to use it +
Historical billing surface: current plan and usage information is available in the app billing area; the initial workspace/settings layout is retired.
Lead status filters distinguished unavailable and paused profiles, while invitation handling retried recoverable LinkedIn dialog failures. Weekly invitation-limit responses stopped being hidden by generic errors.
How to use it +
Use Leads status filters to narrow your list. Invitation handling and clearer limit errors apply automatically.
Workspace settings and connection-note templates were persisted centrally and moved into settings, so configuration was no longer limited to extension-local state.
How to use it +
Historical configuration: connection-note ownership and editing moved again in later updates. Use the current connection-invite editor for a one-off note.
LinkedIn self-profile capture supplied identity details and generated initial reply instructions and commenting topics, reducing the amount of manual AI setup.
How to use it +
Historical setup: these initial profile-generated defaults have evolved into the current account and campaign configuration; the original extension settings flow is retired.
Lead profiles gained more detail and clearer relationship states, including connected, unavailable and outreach-paused profiles. Better profile matching helped reduce duplicate records.
How to use it +
Open Leads and select a person to review their profile and relationship details.
Choose comment identities and monitor live runs
Comment runs gained personal and company identity selection, live progress, run controls and more reliable result reporting. Comments history distinguishes scanned, evaluated, skipped, failed and posted work.
How to use it +
Open Comments, start a one-off run, choose the available commenting identity and inspect the run details as it progresses.