logo
AgentLed

App Actions Reference

How to discover, read, and use app action schemas. Every action has typed inputs, structured outputs, a credit cost, and an auth type — all queryable via MCP.

Discovering Actions

Start with list_apps to find the app, then get_app_actions to get the full schema for all its actions:

// Find apps by name or category
list_apps()

// Get all actions for a specific app
get_app_actions("affinity-crm")

// Result shape:
{
  id: "affinity-crm.resolve-company-by-url",
  name: "Resolve Company by URL",
  description: "Find an Affinity company record by its website URL",
  inputs: [...],
  outputs: [...],
  creditCost: 1,
  creditPricingType: "per-result",
  authentication: { type: "apiKey" }
}

Action IDs follow the format appId.action-name (e.g., hunter.find-email). Use these IDs when configuring workflow steps.

Input Field Types

TypeUse for
stringNames, domains, free-text queries
numberCounts, limits, scores, amounts
booleanFlags, toggles, include/exclude switches
selectFixed-option fields (region, status, type)
multiselectMultiple fixed options (industries, tags)
arrayList of items to process (domains, IDs)
object / jsonStructured payload (request body, config objects)
urlValidated URL fields (company website, profile link)
knowledge-listReference to a Knowledge List by key

Fields marked required: true must be wired; missing required fields block publishing (Validation). Fields with supportsTemplateVariables: true accept {{steps.stepId.field}} syntax.

Authentication Types

Auth typeSetup
oauth2Connect once via OAuth flow in Integrations dashboard. Tokens auto-refresh.
apiKeyPaste key in Integrations → app → Configure. Stored encrypted, workspace-scoped.
agentled-managedNo setup. AgentLed supplies the key; usage billed to workspace credits.
bearer / basicPass token or credentials as step input (use with Custom Actions / HTTP Request).
noneNo credential required. Public API or AgentLed internal action.

Pagination

Apps that return lists (Hunter, Affinity, LinkedIn search) expose pagination parameters in the action schema. Common patterns:

  • •offset / limit — pass offset: 0 then increment by limit each iteration.
  • •cursor — the response includes a nextCursor; pass it to the next call.

Combine pagination with a loop step to walk through large result sets, or with batching to fan out across pages in parallel.

Credits in Execution Logs

Credit deductions are logged per step in the execution timeline. Each step output includes:

  • •creditCost — credits charged for this call.
  • •creditPricingType — per-usage (always charged) or per-result (charged only when a result is returned).

Provider-level rate limits (429s) appear as step errors in the timeline. Combine with Auto-Fix retry to handle transient rate-limit responses automatically.

Testing an Action

Use test_app_action to fire a live request and inspect the response before wiring it into a workflow:

test_app_action("hunter", "find-email", {
  domain: "acme.com",
  first_name: "Jane",
  last_name: "Doe"
})
// Returns live API response — inspect output fields before adding to workflow

Next Steps