Lemlist: Post Deliverability Alerts

Create Deliverability Alert.

Tool ID: lemlist_post_deliverability_alerts

Run this action

Use the TypeScript SDK for a single call. Put ctx.tools.execute(...) inside a Play when the call should be durable, scheduled, or run across a CSV.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'lemlist_post_deliverability_alerts',
  {
    "widget": "warmup",
    "metric": "inboxRate",
    "severity": "warning",
    "scope": "global",
    "threshold": 100,
    "comparisonOperator": "equal",
    "periodDays": 30,
    "periodMode": "rolling"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute lemlist_post_deliverability_alerts --input '{
  "widget": "warmup",
  "metric": "inboxRate",
  "severity": "warning",
  "scope": "global",
  "threshold": 100,
  "comparisonOperator": "equal",
  "periodDays": 30,
  "periodMode": "rolling"
}' --json

Example response

The SDK exposes this shape at result.toolResponse.raw. Values below are representative.

{
  "data": {
    "_id": "_123",
    "teamId": "team_123",
    "createdBy": "example"
  }
}

Use deepline tools get lemlist_post_deliverability_alerts --json for the latest machine-readable contract.

Input reference

Create Deliverability Alert

Name	Type	Required	Default	Details
`payload.widget`	`"warmup" \| "outreach"`	Yes	—	Allowed: `warmup`, `outreach`.
`payload.metric`	`"inboxRate" \| "spamRate" \| "score" \| "deliveryRate" \| "bounceRate"`	Yes	—	Allowed: `inboxRate`, `spamRate`, `score`, `deliveryRate`, `bounceRate`.
`payload.severity`	`"warning" \| "critical"`	Yes	—	Allowed: `warning`, `critical`.
`payload.scope`	`"global" \| "mailbox" \| "domain"`	Yes	—	Allowed: `global`, `mailbox`, `domain`.
`payload.scopeEntities`	`array`	No	—	Required when `scope` is `mailbox` or `domain` and you want to target specific entities. Mailbox entries use the format `userId\|email\|mailboxId`. Domain entries are bare domains (e.g. `acme.com`).
`payload.threshold`	`number`	Yes	—	Minimum: 0. Maximum: 100.
`payload.comparisonOperator`	`"equal" \| "below" \| "above"`	Yes	—	Allowed: `equal`, `below`, `above`.
`payload.periodDays`	`integer`	Yes	—	Minimum: 1. Maximum: 30.
`payload.periodMode`	`"rolling" \| "consecutive"`	Yes	—	Allowed: `rolling`, `consecutive`.
`payload.channelConfig`	`object`	No	—	Notification channels triggered when the alert fires. At least one channel must be enabled. If omitted on creation, defaults to `inapp` only.
`payload.recheckDelayHours`	`integer`	No	—	Cool-down between re-evaluations after the alert triggers, in hours. Defaults to 12.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	A deliverability alert configuration. The alert is evaluated periodically against your warm-up or outreach metrics and triggers notifications through the configured channels (in-app, email, webhook, Slack) when the threshold is breached.
`result.data._id`	`string`	No	—	Unique alert configuration identifier (prefixed with `dac_`).
`result.data.teamId`	`string`	No	—	ID of the team that owns the alert.
`result.data.createdBy`	`string`	No	—	ID of the user who created the alert.
`result.data.createdAt`	`string`	No	—	Creation timestamp. Format: `date-time`.
`result.data.updatedAt`	`string`	No	—	Last update timestamp. Format: `date-time`.
`result.data.widget`	`"warmup" \| "outreach"`	No	—	Data source the alert evaluates. `warmup` checks lemwarm metrics; `outreach` checks campaign-sending metrics. Allowed: `warmup`, `outreach`.
`result.data.metric`	`"inboxRate" \| "spamRate" \| "score" \| "deliveryRate" \| "bounceRate"`	No	—	Metric being monitored. Valid combinations depend on `widget`: `warmup` supports `inboxRate`, `spamRate`, `score`; `outreach` supports `deliveryRate`, `bounceRate`. Allowed: `inboxRate`, `spamRate`, `score`, `deliveryRate`, `bounceRate`.
`result.data.severity`	`"warning" \| "critical"`	No	—	Alert severity. Allowed: `warning`, `critical`.
`result.data.scope`	`"global" \| "mailbox" \| "domain"`	No	—	Aggregation level the metric is computed at. `global` covers all of the workspace’s mailboxes (warm-up only); `mailbox` evaluates each mailbox individually; `domain` groups mailboxes by their sending domain. Allowed: `global`, `mailbox`, `domain`.
`result.data.scopeEntities`	`array`	No	—	Restricts the alert to a subset of entities matching `scope`. When empty, all entities of that scope are checked. For `scope=mailbox`, each entry is a composite string `userId\|email\|mailboxId`. For `scope=domain`, each entry is a domain (e.g. `acme.com`). Ignored when `scope=global`.
`result.data.threshold`	`number`	No	—	Threshold value the metric is compared against (0–100, expressed as a percentage for rate metrics). Minimum: 0. Maximum: 100.
`result.data.comparisonOperator`	`"equal" \| "below" \| "above"`	No	—	How `threshold` is compared to the current value. `below` triggers when the value drops under the threshold; `above` triggers when it exceeds it; `equal` triggers on exact match. Allowed: `equal`, `below`, `above`.
`result.data.periodDays`	`integer`	No	—	Length of the evaluation window, in days (1–30). Minimum: 1. Maximum: 30.
`result.data.periodMode`	`"rolling" \| "consecutive"`	No	—	How the metric is computed over `periodDays`. `rolling` averages the metric across the window; `consecutive` requires the condition to hold on every one of the most recent `periodDays`. Allowed: `rolling`, `consecutive`.
`result.data.channelConfig`	`object`	No	—	Notification channels triggered when the alert fires. At least one channel must be enabled. If omitted on creation, defaults to `inapp` only.
`result.data.channelConfig.email`	`object`	No	—	—
`result.data.channelConfig.email.enabled`	`boolean`	No	—	—
`result.data.channelConfig.email.addresses`	`array`	No	—	Required when `email.enabled` is `true`. At least one valid address.
`result.data.channelConfig.inapp`	`object`	No	—	—
`result.data.channelConfig.inapp.enabled`	`boolean`	No	—	Show the alert in the lemlist app.
`result.data.channelConfig.webhook`	`object`	No	—	—
`result.data.channelConfig.webhook.enabled`	`boolean`	No	—	Send a webhook callback. Requires a webhook subscribed to the `deliverabilityAlertTriggered` event (see Add Webhook).
`result.data.channelConfig.slack`	`object`	No	—	—
`result.data.channelConfig.slack.enabled`	`boolean`	No	—	Send a Slack message. Requires a Slack integration to be connected on the team.
`result.data.enabled`	`boolean`	No	—	Whether the alert is currently active. Disabled alerts are not evaluated.
`result.data.lastCheckedAt`	`string`	No	—	Last time the alert was evaluated. Format: `date-time`.
`result.data.lastTriggeredAt`	`string`	No	—	Last time the alert fired. Format: `date-time`.
`result.data.recheckDelayHours`	`integer`	No	—	Cool-down between re-evaluations after the alert has triggered, in hours. Defaults to 12.
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

Get started

Build and automate

Common workflows

Data and integrations

Reference

Lemlist: Post Deliverability Alerts

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation