Lusha
Enrich contacts with Lusha direct dials and verified email addresses on creation. Field mapping keeps your custom-field schema intact, and bulk re-enrichment covers historical records on demand.
Everything Lusha does inside Strkr.
- Direct dial and verified email on contact-create
- Bulk re-enrich historical records
- Field mapping to custom fields
- Rate-limit aware batch processing
Native code, not a shim.
OAuth where available
Lusha will ship with a native OAuth flow when it lands. No pasted credentials for admins to rotate manually.
KMS-encrypted tokens
Access and refresh tokens are envelope-encrypted at rest using a dedicated customer-managed KMS key. Decryption only happens in Lambda memory during an active API call; plaintext tokens never land in a log.
Shared by the workspace
A workspace admin connects Lusha once; every teammate uses the shared connection without re-authenticating.
Disconnect at any time
Admins or users can disconnect Lusha from inside Strkr. Stored tokens are deleted and the provider's revocation endpoint is called within 24 hours.
Lusha is on the roadmap.
We ship integrations as first-class native code, which takes a little longer than a Zapier shim. If Lusha is a dealbreaker for your evaluation, reply to the welcome email after you start a trial and we'll flag it to the roadmap.