For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
HomepageProduct HelpLog inTry for Free
Developers HomeAPI ReferenceMCP
Developers HomeAPI ReferenceMCP
  • Getting Started
    • Introduction
    • Authentication with API Keys
    • Authentication with OAuth
    • API Clients
    • Pagination
    • Specifying Fields
    • Filter Parameters
    • HTTP Response Codes
    • Rate Limits
    • Timezone Offsets
    • Rich Text Fields
    • Changelog
  • CRM Core
    • Leads
    • Contacts
    • Opportunities
    • Tasks
    • Files
    • Custom Objects
    • Comments
  • Activities
    • Activities
    • Notes
    • Calls
    • Emails
    • Email Threads
    • WhatsApp Messages
    • Meetings
    • Custom Activities
    • Creations
    • Form Submissions
    • Lead Status Changes
    • Opportunity Status Changes
    • Lead Merges
    • Task Completions
  • Events & Webhooks
    • Webhooks
    • Events
  • Search & Reporting
    • Advanced Filtering
    • Smart Views
    • Reporting
  • Automation & Bulk Actions
    • Sequences (Workflows)
    • Bulk Actions
    • Exports
    • AI Field Enrichment
  • CRM Configuration
    • Custom Fields
    • Custom Activity Types
    • Custom Object Types
    • Pipelines
    • Opportunity Statuses
    • Lead Statuses
    • Integration Links
    • Forms
  • Communication Configuration
    • Email Templates
    • SMS Templates
    • Outcomes
    • Playbooks
    • Scheduling Links Guide
    • Scheduling Links
    • Connected Accounts
    • Send As
    • Unsubscribed Emails
    • Phone Numbers
    • Blocked Phone Numbers
    • Dialers
  • Users & Organizations
    • Users
    • Organizations
    • Memberships
    • Roles
    • Groups
Close

Product

OverviewCommunicationAutomationIntegrationsReportingSMSCallingSecurityForms

Pricing & Use Cases

PricingClose vs Other CRMsCustomer Stories

Resources

Sales BlogSales ResourcesSales GuidesWebinarsOn-Demand DemoSales Tools

Company

AboutCareersPartner with CloseBrand GuidelinesTermsPrivacyGDPRCCPA

Get Help

+1-833-GO-CLOSEHelp CenterDownload the Close AppProduct UpdatesSystem Status
LogoLogo
HomepageProduct HelpLog inTry for Free
On this page
  • Lead filtering
  • Pausing and resuming
  • Receiving an email when done
Automation & Bulk Actions

Bulk Actions

Perform bulk operations on leads matching a search query or smart view.
||View as Markdown|
Was this page helpful?
Edit this page
Previous

Update a specific Subscription

Next

List bulk emails

Built with

Bulk actions let you email, edit, delete, or subscribe leads in bulk.

Lead filtering

To initiate bulk actions for a subset of leads, provide the structured filtering values from the Advanced Filtering API such as query, results_limit, and sort fields. The only difference is that Bulk Actions endpoints require you to rename the query field to s_query (shorthand for structured query).

For example, this is the payload you would send to the Advanced Filtering API:

1{
2 "query": {
3 "queries": [...]
4 },
5 "results_limit": 100,
6 "sort": [{...}]
7}

And this is the equivalent Bulk Actions payload (note query -> s_query):

1{
2 "s_query": {
3 "queries": [...]
4 },
5 "results_limit": 100,
6 "sort": [{...}]
7}

Pausing and resuming

You can pause an in-progress bulk action by sending { "status": "paused" }. You can resume it afterwards with { "status": "resuming" }, unless more than 7 days have passed since you paused the action.

Receiving an email when done

By default a confirmation email is sent when a bulk action completes. Set "send_done_email": false in the request if you don’t want this.