Sequencer Campaign Config

What it does

Sequencer campaign settings have a specific failure shape: some fields are dropped silently at creation and must be set in a second update call, and some values that look valid are rejected or, worse, stored as a literal zero. This skill sets the configuration in the order that survives, then reads it back and diffs it against what was intended.

When to use it

• set up a campaign in my sequencer
• my campaign settings did not save
• sending at the wrong time
• configure tracking and limits
• campaign schedule

What it needs from you

• platform: which sending platform
• schedule: sending days, hours and the recipient timezone
• limits: per account daily limit and campaign level caps
• tracking: open and click tracking preference

Live data it reads

Pushing a finished list into the sequencer can run through the Mamba Labs push actor rather than a manual CSV, which keeps the field names identical between the enrichment table and the campaign payload. - clay-to-instantly-smartlead-push: push enriched rows into a sequencer campaign with the field names preserved Store page: https://apify.com/mambalabs/clay-to-instantly-smartlead-push Runnable example input:

How it works

1. Create the campaign with the minimum viable settings, then set the rest in a second update. Fields dropped at creation are the most common cause of a campaign that sends with tracking on when tracking was meant to be off.
2. Set the timezone with the exact identifier the platform accepts. Platform timezone enums are not the standard database list and a rejected value falls back to a default silently on some platforms.
3. Distinguish clearing a field from setting it to zero. On several platforms null removes the setting and zero stores a literal zero, which is a hard cap of nothing.
4. Turn open tracking off unless there is a specific reason for it. Tracking pixels cost deliverability and the metric they produce is unreliable.
5. Set the daily limit per account below the platform maximum, leaving headroom for follow up steps already in flight.
6. Read the campaign back through the API or the interface and diff every field against the intent. This step is the point of the skill.
7. Send one test to a seed address on a different provider and read the raw source, not the rendered preview.

What you get back

The configuration as set, the read back diff with any field that did not stick, and the seed test result.

The quality bar

• Configuration is read back and diffed, not assumed
• The timezone identifier used is one the platform accepts
• Null and zero are treated as different values and this is stated
• A seed test is sent and its raw source is read

Where it runs

• Claude Code
• Codex CLI
• Cursor
• MCP-compatible agents