More reliable lead and account recovery · Filter custom fields and track company changes
More reliable lead and account recovery
What changed
Deleting a lead or disconnecting a LinkedIn profile now clears related work more reliably. Follow-ups, Inbox refreshes and account recovery also handle interruptions more consistently.
How to use it
No setup is needed. Follow the sign-in recovery instructions shown for the affected LinkedIn account, and check the final status of deleted leads or interrupted tasks.
Filter custom fields and track company changes
What changed
Lead and company API searches now filter custom text fields with exact, list, contains and empty-value conditions. Webhook and MCP event contracts add company and custom-field changes so integrations can follow actual updates.
How to use it
Pass customFieldFilters to listLeads or listCompanies. Subscribe to the relevant supported change events; custom-field conditions are not yet supported in saved dynamic-audience rules.
Keep visible leads when search results are limited
What changed
Identifiable profiles from a search page are retained when LinkedIn hides other cards behind a paywall. Search status exposes account restrictions so a completed run is not mistaken for complete access.
How to use it
Run the search normally and review any account-restriction notice before treating the results as exhaustive.
Let sequences continue after optional endorsements
What changed
Skill parsing and acknowledgement handling are corrected, and optional endorsement-step settlement lets the follow-up continue after success, skip or failure. Localized empty skills are recognized without treating malformed responses as empty lists.
How to use it
No setup is needed for enabled endorsement steps. Inspect the step result if an endorsement is skipped or fails.
Improve OAuth compatibility and typed MCP tools
What changed
OAuth scope registration follows one resource-aware policy across clients, and eligible connections can refresh after explicit workspace consent. MCP tools expose parameter types and clearer directory titles.
How to use it
Connect your assistant through the existing Relinta sign-in flow. New client registrations must request supported scopes; approving the workspace remains required.
Preserve work while the app refreshes
What changed
Background data refreshes and app updates better preserve table selections, visible records and the first edits made in a form. Responsive navigation and collapsing headers avoid several overflow and scrolling issues.
How to use it
No setup is needed. Save or finish active edits before accepting an app update when the interface asks you to refresh.