EmailBison: Update Daily Warmup Limits For Email Accounts

Set daily warmup email and reply limits for selected EmailBison sender accounts.

Tool ID: emailbison_update_daily_warmup_limits_for_email_accounts

Run this action

Use the TypeScript SDK for one call. Use ctx.tools.execute(...) inside a Play for durable calls, scheduled calls, or CSV processing.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'emailbison_update_daily_warmup_limits_for_email_accounts',
  {
    "sender_email_ids": [
      123
    ],
    "daily_limit": 123
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute emailbison_update_daily_warmup_limits_for_email_accounts --input '{
  "sender_email_ids": [
    123
  ],
  "daily_limit": 123
}' --json

Example response

The SDK returns this shape at result.toolResponse.raw. The example values illustrate the response.

{
  "data": {
    "data": {
      "success": true,
      "message": "Example message"
    }
  }
}

Use deepline describe emailbison_update_daily_warmup_limits_for_email_accounts --json for the latest machine-readable contract.

Input reference

This endpoint updates the daily warmup limits for selected email accounts

Name	Type	Required	Default	Details
`payload.sender_email_ids`	`array`	Yes	—	Array of sender email IDs.
`payload.daily_limit`	`integer`	Yes	—	The daily limit of warmup emails to send
`payload.daily_reply_limit`	`integer \| string`	No	—	The daily limit of warmup reply emails. You can pass an “auto” string to set this to auto. WARNING: You should only use this section if explicitly told by your inbox reseller. We cannot be held responsible if you experience low inbox health as a result of controlling your own reply rate.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.data`	`object`	No	—	—
`result.data.data.success`	`boolean`	No	—	—
`result.data.data.message`	`string`	No	—	—
`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.

​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