Integration
Connect lemlist to Dixa
When New Activity fires in lemlist, your agent runs Set Custom Contact Attributes in Dixa. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want lemlist and Dixa to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What lemlist can start in Dixa
When New Activity in lemlist
then Set Custom Contact Attributes in Dixa
When New Activity in lemlist
then Add Internal Note in Dixa
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with lemlist and Dixa
Triggers and actions 1 trigger · 31 actions
Trigger
New ActivityTriggers when an activity has ocurred. It can be an email has been sent, replied to, bounced, or unsubscribed from or v3 new activity like a LinkedIn profile have been visited or a phone call just ended.
Action
Add Recipient to Unsubscribe ListAdd a recipient to the unsubscribe list.
Action
Mark a Lead From All Campaigns as InterestedMark a Lead From All Campaigns as Interested.
Action
Mark a Lead From One Campaign as InterestedMark a Lead From One Campaign as Interested.
Action
Remove Lead From CampaignRemove a Lead from a campaign.
Action
Remove Lead From UnsubscribeRemove a Lead from unsubscribe.
Action
Resume Lead From All or Specific CampaignsResume Lead From All or Specific Campaigns.
Action
Search LeadSearch a lead.
Action
Update Lead From CampaignUpdate Lead From Campaign.
Action
Add Internal NoteAdds an internal note, visible only to agents, to a Dixa conversation and returns the created note.
Action
Change Conversation StatusChanges a conversation's status by closing it, reopening it, or putting it into follow-up until a chosen time.
Action
Create Callback RequestCreates a callback request conversation in Dixa, placing a call-back for an end user into the chosen queue, and returns the new conversation's id.
Action
Create ConversationCreates a new Dixa conversation on the email, contact form, chat, SMS, WhatsApp or callback channel and returns its ID.
Action
Create UserCreates an end user (contact) in Dixa with their name, contact details and any custom contact attributes, and returns the new end user.
Action
Get Anonymization StatusReturns the status of an anonymization request submitted earlier for a user, conversation or message, including when it was initiated and when it was processed.
Action
Get Conversation by IdReturns a single Dixa conversation by its id, including its channel, state, assignment, queue and custom attributes.
Action
Get Conversation RatingReturns the latest rating statuses and scores for a conversation, with one entry for each question of the survey.
Action
Get Conversation TagsReturns the tags applied to a conversation, including each tag's name, color and state.
Action
Get Messages in ConversationReturns all messages in a Dixa conversation, sorted from oldest to newest.
Action
Get Queue by IdReturns a Dixa queue by its id, including its name, offering settings, thresholds and the channels that use it. An error occurs if the queue is not found.
Action
Get User by IdReturns one Dixa end user (contact) by id, including their name, email addresses, phone numbers, external id and custom attribute values.
Action
Remove Tag From ConversationRemoves a tag from a Dixa conversation. Active and inactive tags can both be removed.
Action
Search ConversationReturns the conversations that contain the specified text, match the specified filters, or both, with snippets showing where the text was found.
Action
Search Conversations by UserReturns the conversations requested by a specific end user.
Action
Search Enduser by External IDReturns the end users whose external ID matches the value you provide.
Action
Search User by Email AddressReturns the Dixa end users whose email address matches the one you provide.
Action
Search User by Phone NumberReturns the Dixa end users whose phone number matches the one you specify.
Action
Set Custom Contact AttributesSets custom attribute values on an end user in Dixa and returns the attributes that were updated.
Action
Set Custom Conversation AttributesSets the values of custom attributes on a conversation and returns the conversation's updated custom attributes.
Action
Tag ConversationAdds an existing active tag to a conversation.
Action
Transfer Conversation to QueueTransfers a conversation to the queue you choose, optionally on behalf of a specific agent, admin or AI agent.
Action
Update End UserUpdates an end user's name, contact details, avatar, external ID and custom contact attributes in Dixa. Only the fields you fill in are changed.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from lemlist
lemlist to RefinerRefiner is a customer survey tool for data driven SaaS teams.
lemlist to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
lemlist to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
lemlist to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
lemlist to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
lemlist to MailchimpMailchimp marketing automation and email platform.
More into Dixa
HubSpot to DixaHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to DixaSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to DixaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to DixaGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to DixaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to DixaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
lemlist and Dixa, answered
What can start an automation from lemlist?
Any of lemlist's 1 trigger in the catalog, including New Activity. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Dixa when something happens in lemlist?
Any of Dixa's 23 actions, including Create Callback Request, Create Conversation, Create User and Update End User. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Dixa to lemlist?
Dixa has no triggers in the catalog today, so automations start in lemlist. If you need the other direction, ask: your agent reads Dixa's API documentation and adds it.
Do I have to build a connector for lemlist or Dixa?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use lemlist and Dixa without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.