Leadping Automations API

Manages automated lead follow-up workflows and their execution history. Use these endpoints to configure SMS automation steps, preview eligible leads, run workflows, and inspect individual automation executions.

Operations 9

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

POST /automations Create a lead follow-up automation · Create an organization lead follow-up automation #
Ask an LLM
“How do I set up an automation that follows up with new leads?”
“Can I build a follow-up workflow with triggers and message steps?”
Tell an agent
Create a new follow-up automation named {name}.
Set up automation {name} with these triggers: {triggers}.
PUT /automations/{id} Update a follow-up automation · Update an organization lead follow-up automation #
Ask an LLM
“How do I change the triggers on an existing automation?”
“Can I disable an automation without deleting it?”
Tell an agent
Rename automation {id} to {name}.
Turn automation {id} (named {name}) enabled={enabled}.
GET /automations/{id} Get a follow-up automation · Get an organization lead follow-up automation #
Ask an LLM
“Which triggers and message steps does this automation use?”
“Can I check whether a specific automation is enabled?”
Tell an agent
Show me the configuration of automation {id}.
Look up automation {id} and tell me if it's turned on.
DELETE /automations/{id} Delete a follow-up automation · Delete an organization lead follow-up automation #
Ask an LLM
“How do I permanently remove an automation so it stops scheduling follow-ups?”
“What happens to lead follow-up when I delete an automation?”
Tell an agent destructive · confirm first
Delete automation {id}.
Remove the follow-up automation {id} for good.
GET /automations/{id}/runs List an automation's recent runs · Gets recent persisted execution runs for an automation console #
Ask an LLM
“How can I see the recent execution history of an automation?”
“Did my automation actually run recently, and what state did the runs end in?”
Tell an agent
List recent runs of automation {id}.
Show the run history console for automation {id}.
GET /automations/{id}/runs/{runId} Get one automation run · Gets one persisted automation execution run for its console #
Ask an LLM
“Can I inspect the console state of a single automation run?”
“What happened during a specific execution of my automation?”
Tell an agent
Show run {runId} of automation {id}.
Open the console for automation {id} execution {runId}.
POST /automations/all/my List my follow-up automations · List organization lead follow-up automations #
Ask an LLM
“Which follow-up automations do I have in Leadping?”
“Can I search my automations by name and sort them?”
Tell an agent
List all my automations.
Search my automations for {search}.
POST /automations/preview Preview an automation on a sample lead · Preview a lead follow-up automation #
Ask an LLM
“Can I test what an automation would send before turning it on?”
“Is there a way to only validate an automation's configuration without evaluating it?”
Tell an agent
Preview this automation draft against a sample lead: {automation}.
Validate automation draft {automation} with validate_only={validate_only}, skipping conditions and actions.
POST /automations/{id}/run Run an automation manually · Runs an automation through its Manual trigger #
Ask an LLM
“How do I kick off an automation by hand through its manual trigger?”
“Can I start an automation run right now instead of waiting for a trigger?”
Tell an agent
Run automation {id} now using its manual trigger.
Manually start automation {id}.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/leadping:leadping-automations-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

leadping-automations-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Leadping Automations API
  description: The Leadping API helps businesses capture and manage leads, automate follow-up, send SMS and MMS messages, place calls, track conversations, enforce contact suppression, and analyze communication workflows. Use this OpenAPI 3.1 contract to integrate lead sources, build organization tools, or generate a typed API client. Authenticate protected operations with a Leadping user access token or WorkOS organization API key. Lead intake operations also accept a Leadping source key.
  termsOfService: https://leadping.ai/docs/terms-of-service
  contact:
    name: Leadping Support
    url: https://leadping.ai/contact
    email: support@leadping.ai
  license:
    name: MIT
    url: https://opensource.org/licenses/MIT
  version: v1
  summary: Lead management, messaging, calling, and automation API
servers:
- url: https://api.leadping.ai
  description: Production
tags:


# --- truncated at 32 KB (77 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/leadping/refs/heads/main/openapi/leadping-automations-api-openapi.yml