1. Actions unavailable after installing the app
TL;DR: Go to [Settings] → [Apps] → [Installed] → [lemlist] in Attio and complete the [Workspace connection] step with your API key. Verify by opening a workflow — lemlist triggers and actions should now appear.
Symptoms
lemlist appears under installed apps but doesn't show up in the workflow builder
No lemlist trigger events or action steps are available when building a workflow
The integration page shows the app installed but the connection section is empty or disconnected
Steps
Go to [Settings] → [Apps] → [Installed] in Attio
Click [lemlist]
Locate the [Workspace connection] section
Enter your lemlist API key and click [Save]
✅ Verify: A success message appears and the connection shows as active
Open a workflow and check the trigger or action block
✅ Verify: lemlist event types and action steps appear in the selection list
Confirm it's fixed
✓ lemlist trigger events appear in the workflow trigger picker
✓ lemlist action steps are selectable in workflow steps
✓ Connection shows as active in [Settings] → [Apps] → [Installed] → [lemlist]
Why it happens
Installing the lemlist app from the Attio marketplace adds the listing but doesn't complete authentication. The workspace connection must be completed separately using a lemlist API key.
2. Can't retrieve the API key
TL;DR: Generate a new key in lemlist at [Settings] → [Integrations] → [API & Webhooks]. Copy it immediately — it's shown only once — then paste it into the Attio [Workspace connection] field.
Symptoms
The Workspace connection field in Attio shows blank or disconnected
A previously working connection stopped authenticating
The API key modal was closed before the key was copied
Steps
Go to lemlist [Settings] → [Integrations] → [API & Webhooks]
Click [Generate new key]
Copy the full key immediately — it is shown only once
Go to Attio [Settings] → [Apps] → [Installed] → [lemlist]
Paste the key into [Workspace connection] and click [Save]
✅ Verify: Connection status updates to active
Confirm it's fixed
✓ Workspace connection shows active in Attio
✓ lemlist actions reappear in the workflow builder
✓ Existing lemlist workflows resume triggering
Why it happens
lemlist shows API keys once for security. After closing the modal, the key cannot be retrieved — only regenerated. Generating a new key immediately invalidates the previous one.
3. Contact not added to campaign
TL;DR: Check if the contact is already enrolled in that campaign in lemlist. If not, confirm the Attio record has a valid email address, then retry enrollment.
Symptoms
Enrollment action completes without error but the contact doesn't appear in the lemlist campaign
"Contact already enrolled" message appears
Bulk enrollment runs but some contacts are missing from the campaign
Steps
Open the contact record in Attio and confirm an email address is populated
In lemlist, search for the contact and check if they're already enrolled in this campaign
If already enrolled: use a different campaign, or remove them from the current one first
If not enrolled and email is missing: add the email address to the Attio person record
Retry enrollment for a single contact before running a batch
✅ Verify: The contact appears in the lemlist campaign list within 30 seconds
Confirm it's fixed
✓ Contact appears in the campaign in lemlist
✓ Campaign sequence shows the contact queued for outreach
Why it happens
lemlist prevents duplicate enrollment to protect sender reputation. Enrollment also silently fails if the email field is missing — a valid email address is required to add any contact to a campaign.
4. Workflow not triggering
TL;DR: Open the workflow trigger block and confirm the [Event type] matches exactly what occurred in lemlist. Confirm the workflow status is [Published] — not [Draft].
Symptoms
Workflow is configured but never fires after lemlist campaign activity
CRM records aren't updating after contacts reply or show interest
Tasks or Slack notifications aren't being created when expected
Workflow run history is empty
Steps
Open the Attio workflow
Click the trigger block and review the [Event type] selected
Match it to the exact action that occurred in lemlist — "Reply received" and "Email clicked" are different events
Check the workflow status bar at the top of the page
If the status shows [Draft]: click [Publish]
Test by performing the trigger action in lemlist — for example, manually marking a contact as interested
✅ Verify: Go to [Run history] and confirm a new execution appears within 2 minutes
Confirm it's fixed
✓ A new entry appears in Run history after the trigger action
✓ CRM fields, tasks, or notifications update as expected after the workflow fires
Why it happens
Event type names must match exactly — "Campaign completed" and "Sequence finished" refer to different states. Workflows in Draft status only run during manual testing, not from live lemlist activity.
5. CRM data not enriching automatically
TL;DR: Add [Find email], [Get LinkedIn data], or [Verify email] action steps to an Attio workflow triggered by [Person created] or [Person updated], then publish the workflow.
Symptoms
New contacts arrive in Attio with email, phone, or LinkedIn fields missing
Records from imports still require manual research
Enrichment only runs when triggered manually from a contact record
Steps
Go to [Automation] → [Workflows] in Attio
Create a new workflow or open the one covering your contact source
Set the trigger to [Person created] for new contacts or [Person updated] for record changes
Add a [Find email] action step → map the output to the [Email] field on the person record
Add [Get LinkedIn data] → map the output to the [LinkedIn URL] field
Optionally add [Verify email] after [Find email] to flag undeliverable addresses before they enter a campaign
Click [Publish]
✅ Verify: Create a test contact — email and LinkedIn URL should populate automatically within 1–2 minutes
Confirm it's fixed
✓ New contacts have email and LinkedIn URL populated automatically
✓ Verify email marks addresses as deliverable or unverifiable
✓ Workflow Run history shows a triggered run for each new contact
Why it happens
Enrichment actions aren't added to Attio workflows by default. Each contact source entering Attio needs its own trigger — inbound form fills and CSV imports may require separate workflows to cover both.
Escalate if unresolved
Contact lemlist support with: your Attio workspace domain, the exact step or action that's failing, a screenshot of any error or disconnected status, and the timestamp of the failed workflow run
If a workflow ran but produced wrong output: share the Run history entry, the full workflow configuration, and the lemlist campaign or contact ID involved