Sequence sending rules

List the sending rules of sequences

crm.sequences.rulesets.list

Lists the organization's sending rules for sequences, the default first and then by name: what pauses or finishes a contact (triggers: account_reply_delay and a phone call after repeated opens; contact_triggers: finish on link click, mark unresponsive after N days), emails skipped by contact or account labels (email_triggers), and throttling (the CC and BCC addresses copied on every sequence email, ignore_bounce_protection), with who created them (created_by_id, created_by_name). A reply, an unsubscribe and a bounce always finish the contact, whatever the rules say. The sending pace is set by the schedules (crm.sequences.schedules.list). A sequence uses one through its ruleset_id; new sequences get the default. Paginated by cursor (limit up to 100, the default). Requires view access to the CRM.

Scope

crm:read

Permission

View the module

MCP tool

crm_sequences_rulesets_listOn the full surface; on the compact one, mb_execute_operation with id: "crm.sequences.rulesets.list".

Declared cost: up to 101 reads and 0 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl "https://api.mb-suite.com/v1/crm/sequence-rulesets" \
  -H "Authorization: Bearer $MB_API_KEY"

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl "https://api.mb-suite.com/v1/crm/sequence-rulesets" \
  -H "Authorization: Bearer $MB_TEST_KEY"

Create sending rules for sequences

crm.sequences.rulesets.create

Creates sending rules for sequences: a name and, optionally, triggers, contact_triggers, email_triggers and throttling (each group left out takes the standard set: pause 24 h after an account reply, mark unresponsive after 30 days, no CC or BCC, bounce protection on). is_default true makes them the organization's default (new sequences get them) and unsets the previous default. It is not assigned to any sequence: set ruleset_id with crm.sequences.update. Returns ruleset_id. Manager-tier only (manage_sequence_settings: owner, admin, crm_admin or sales_manager).

Scope

crm:write

Permission

Edit in the module · CRM action: manage_sequence_settings

MCP tool

crm_sequences_rulesets_createOn the full surface; on the compact one, mb_execute_operation with id: "crm.sequences.rulesets.create".

Declared cost: up to 5 reads and 3 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl -X POST "https://api.mb-suite.com/v1/crm/sequence-rulesets" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "name": "NAME"
}'

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl -X POST "https://api.mb-suite.com/v1/crm/sequence-rulesets" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "name": "NAME"
}'

Update sending rules

crm.sequences.rulesets.update

Updates sending rules; send at least one key in updates (name, is_default, triggers, contact_triggers, email_triggers, throttling: each group replaces the whole group). Every sequence that uses them follows the new rules from its next send. Changing the CC/BCC addresses or the bounce protection is also recorded as a security event. is_default true moves the default here. Not found (sequence_ruleset_not_found) if the id does not exist. Manager-tier only (manage_sequence_settings).

Scope

crm:write

Permission

Edit in the module · CRM action: manage_sequence_settings

MCP tool

crm_sequences_rulesets_updateOn the full surface; on the compact one, mb_execute_operation with id: "crm.sequences.rulesets.update".

Declared cost: up to 5 reads and 3 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl -X PATCH "https://api.mb-suite.com/v1/crm/sequence-rulesets/{ruleset_id}" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "updates": {}
}'

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl -X PATCH "https://api.mb-suite.com/v1/crm/sequence-rulesets/{ruleset_id}" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "updates": {}
}'

Delete sending rules

crm.sequences.rulesets.delete

Deletes sending rules; the sequences that used them are left without sending rules (the result says how many). It does not go to the trash. Outside the screen it requires a dry run (which lists the affected sequences) and a confirm_token, and a credential that allows deleting. Not found (sequence_ruleset_not_found) if the id does not exist. Manager-tier only (manage_sequence_settings).

Needs confirmation: first dry_run: true (preview and confirm_token, valid 10 minutes and for one run), then the same body with confirm_token. In a few operations only with certain data: the description says when. Why and how: Dry run and confirm_token.

Scope

crm:write and “Allow deletions” (crm:delete in OAuth)

Permission

Edit in the module · CRM action: manage_sequence_settings

MCP tool

crm_sequences_rulesets_deleteOn the full surface; on the compact one, mb_execute_operation with id: "crm.sequences.rulesets.delete".

Declared cost: up to 101 reads and 101 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl -X DELETE "https://api.mb-suite.com/v1/crm/sequence-rulesets/{ruleset_id}" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "dry_run": true
}'

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl -X DELETE "https://api.mb-suite.com/v1/crm/sequence-rulesets/{ruleset_id}" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "dry_run": true
}'