Integration

Connect lemlist to Xitoring

When something happens in lemlist, your agent does the next thing in Xitoring. Describe it in plain language and the automation is built, tested on every branch and kept running.

lemlist1 triggerlemlist8 actionsXitoring16 actions

Browse all apps

Build it

What do you want lemlist and Xitoring to do together?

Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Or work from Claude Code

Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.

Connect Claude Code

Everything your agent can do with lemlist and Xitoring

Triggers and actions 1 trigger · 24 actions

Trigger
New Activity
Triggers 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 List
Add a recipient to the unsubscribe list.
Action
Mark a Lead From All Campaigns as Interested
Mark a Lead From All Campaigns as Interested.
Action
Mark a Lead From One Campaign as Interested
Mark a Lead From One Campaign as Interested.
Action
Remove Lead From Campaign
Remove a Lead from a campaign.
Action
Remove Lead From Unsubscribe
Remove a Lead from unsubscribe.
Action
Resume Lead From All or Specific Campaigns
Resume Lead From All or Specific Campaigns.
Action
Search Lead
Search a lead.
Action
Update Lead From Campaign
Update Lead From Campaign.
Action
Add check
Create a new uptime/website/server check. POST /api/v2/check
Action
Add group
Store a new check/server group. POST /api/v2/groups
Action
Add heartbeat
Create a new heartbeat check. POST /api/v2/heartbeat/add
Action
Add maintenance schedule
Create a new maintenance window. POST /api/v2/maintenance-schedules/add
Action
Add ticket
Create a new support ticket. POST /api/v2/tickets
Action
Delete check
Delete a check. DELETE /api/v2/checks/{id}
Action
Delete server
Remove a server from monitoring. DELETE /api/v2/servers/{id}
Action
Get check
Retrieve a single check by id. GET /api/v2/check/{id}
Action
Get incident
Get a single incident's data. GET /api/v2/incidents/{id}
Action
Get server
Retrieve a single server by id. GET /api/v2/servers/{id}
Action
List checks
List all checks. GET /api/v2/check/
Action
List groups
List all groups. GET /api/v2/groups
Action
List maintenance schedules
List maintenance schedules. GET /api/v2/maintenance-schedules
Action
List servers
List all monitored servers. GET /api/v2/servers
Action
Resolve incident
Resolve an open incident. POST /api/v2/incidents/{id}/resolve
Action
Update check
Update an existing check. PUT /api/v2/check/{id}

Each app on its own

The other way round: Xitoring to lemlist