Skip to main content
Glama

workflow_create

Create automated workflows in Apollo.io that trigger actions based on events or schedules for contacts, accounts, or opportunities.

Instructions

    Create a new workflow automation.

    Workflows trigger actions based on events or schedules.

    Args:
        name: Workflow name
        trigger_type: "event" or "schedule" (default: "event")
        model_type: "Contact", "Account", or "Opportunity" (default: "Contact")
        trigger_events: List of trigger events (for event-based workflows):
            - "contact_saved_or_created" - When a contact is saved/created
            - "contact_updated" - When contact fields change
            - "contact_added_to_list" - When added to a list
            - "contact_added_to_sequence" - When added to a sequence
            - "contact_finished_sequence" - When sequence completes
            - "contact_changed_jobs" - When job change detected
            - "call_logged" - When a call is logged
        actions: List of actions to perform. Each action has:
            - type: "add_to_sequence", "add_to_list", "update_field",
                   "create_task", "send_webhook", "remove_from_sequence"
            - config: Action-specific configuration
        enrollment_filters: Filters to determine which contacts qualify
        active: Whether to activate immediately
        first_run_on: Date for first run (ISO format, e.g., "2026-01-08").
                     Required for schedule-based workflows.

    Returns:
        Created workflow details

    Example:
        workflow_create(
            name="New Lead Nurture",
            trigger_type="event",
            trigger_events=["contact_saved_or_created"],
            actions=[
                {"type": "add_to_sequence", "config": {"sequence_id": "abc123"}}
            ]
        )
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
trigger_typeNoevent
model_typeNoContact
trigger_eventsNo
actionsNo
enrollment_filtersNo
activeNo
first_run_onNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden. It discloses that this creates a new workflow (a write operation) and mentions activation behavior via the 'active' parameter. However, it lacks details on permissions needed, error conditions, rate limits, or whether creation is idempotent, which are important for a creation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections (Args, Returns, Example) and uses bullet points for readability. However, it's somewhat lengthy due to the comprehensive parameter explanations, which are necessary given the 0% schema coverage. Every sentence earns its place by providing essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (8 parameters, creation operation) and 0% schema coverage, the description does an excellent job explaining parameters and includes an example. With an output schema present, it doesn't need to detail return values. The main gap is lack of behavioral context like permissions or error handling, which lowers the score slightly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, so the description must fully compensate. It provides detailed semantics for all 8 parameters: explains each parameter's purpose, lists allowed values for trigger_type and model_type, enumerates trigger_events with descriptions, describes actions structure, and clarifies requirements like first_run_on for schedule-based workflows. This adds significant value beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Create') and resource ('new workflow automation'), with additional context about workflows triggering actions based on events or schedules. It distinguishes from siblings like workflow_create_from_template (template-based creation) and workflow_update (modification).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use this tool through its parameter explanations (e.g., trigger_type choices, first_run_on for schedule-based workflows). However, it doesn't explicitly state when to choose this over alternatives like workflow_create_from_template or workflow_update, nor does it mention prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BlockchainRev/apollo-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server