Skip to main content
Human guide: work with your agent → Inspect one Instantly action before starting provider-backed work. Your first result is a verified input and output contract.

​
Provider-specific requirements

Use Instantly for campaign activation and lightweight outbound reporting.
  • Resolve campaign IDs from list_campaigns before any add operation.
  • For instantly_create_campaign, do not brute-force timezone guesses. Reuse a known-good timezone from an existing campaign via instantly_get_campaign when possible.
  • If the requested timezone is not directly accepted, map it to the closest supported Instantly value before sending. Example: use America/Detroit when the user asks for America/New_York.
  • Treat UTC as unsupported by Instantly create-campaign. Use a supported UTC-equivalent enum value from existing campaigns instead of sending literal UTC.
  • For campaign_schedule.schedules[].days, use numeric day keys ("0".."6"). Named weekdays are normalized by Deepline, but values outside sunday..saturday are rejected.
  • list_leads accepts both campaign and campaign_id (alias). It also supports list_id, in_campaign, in_list, and search filters. Omit all filters to list leads globally.
  • Insert in controlled batches and re-check campaign stats after writes.
  • Keep activation behind enrichment/verification gates to reduce low-quality sends.

​
Find an applicable action

Confirm your effective workspace, then search the live catalog:
Search returns candidates. Check the returned provider and operation rather than selecting a similar title automatically.

​
Inspect the selected contract

Replace <returned-tool-id> with the identifier returned by discovery:
These commands do not execute the selected provider action. Read its required inputs, supported access mode, pricing unit, outputs, and limits. A connection does not establish that every action supports BYOK. Follow the provider-specific requirements above and the live action contract.

​
Prepare one reviewed input

Use one authorized record that matches the inspected schema. Preserve its source identity and define the result you will accept. Open the action reference for its payload and response shape. Provider-backed execution can incur usage or external effects. For reusable logic, follow Write Plays. For direct-call recovery, use Tool execution recovery.
Continue only when the workspace, provider, required fields, acceptance rule, and applicable price are understood. Keep unavailable access separate from no-result evidence.