Ongage Airis

Copies an existing automation workflow into a new draft with new node IDs, named 'Copy of <original name>' unless a name is given. Use when the user wants a variant of an existing automation. The original is not changed and the copy does not run.

duplicate_workflow

Changes a stored email message: name, subject, HTML content, preheader, sender details or tags. Use when the user asks to edit an existing email. If the message has already been sent, Ongage saves the change as a new copy and returns its ID; campaigns and workflows keep using the original until they are repointed.

edit_email_message

Returns the reference for building Contacts Activity reports: the filters format and operators, how field, segment and campaign names resolve, contact status, date-range rules and the report columns. Use before create_contact_activity_report.

get_contact_activity_schema

Returns the Ongage account's default list ID and its contact, user and list counts. Use when a tool needs a list ID the user did not give, or when the user asks how large the account is.

get_account_info

Returns one automation workflow's full configuration: triggers, actions, conditions and status. Use when the user asks how a specific automation works, or to check a workflow after creating it.

get_workflow

Returns one campaign's details: schedule, segments, email message, distribution and status. Use when the user asks about a specific campaign and you have its ID (from list_campaigns) and list ID.

get_campaign

Returns one stored email message, including its subject and full HTML content. Use when the user wants to read, review or preview a specific email and you have its ID (from list_email_messages).

get_email_message

Returns one Ongage Event's configuration: triggers and recurrence, schedule, included and excluded segments, distribution and send-time settings. Use when the user asks how a specific recurring or triggered campaign is set up.

get_event_campaign

Returns performance for Ongage Events (sends, opens, clicks, bounces, complaints, unsubscribes, CTR) over a date range, in the account time zone by default. Use when the user asks how their recurring or triggered campaigns are performing.

get_event_campaign_analytics

Returns one segment's criteria and settings. Use when the user asks how a specific segment is defined and you have its ID (from list_segments).

get_segment

Returns message-level performance for automation workflows over a date range (last 2 weeks by default), for one workflow or all of them. Use when the user asks how their automations are performing.

get_workflow_analytics

Returns the reference for the Ongage automation workflow JSON format: node types and fields, socket and label rules, criteria format, graph constraints, the status machine and worked examples. Use before writing the nodes for create_draft_workflow.

get_workflow_schema

Lists the Contacts Activity reports on a contact list (ID, title, status, row count, dates, filters); expired reports are not listed. Use when the user asks about existing reports, or to find a report's ID.

list_contact_activity_reports

Lists automation workflows (id, name, status, list, trigger type, dates) with search, filters and paging. Results are oldest first unless order is 'desc'. Use when the user asks which automations exist or refers to one by name; use get_workflow for its full graph.

list_workflows

Resolves browser, operating system and country names to the values used in behavioral criteria (numeric IDs for browsers and OS, ISO2 codes for countries). Use when segment or workflow criteria filter by browser, OS or country. OS and country apply only to clicked/opened criteria; browsers do not apply to sent.

list_behavioral_criteria_options

Lists the campaigns one specific input accepts (a report filter, a segment behavioral rule, a workflow trigger, criterion or send node), as the Ongage UI picker for that input offers them. Use when filling a campaign ID into a report, segment rule or workflow node; those inputs reject some campaigns that list_campaigns returns.

list_campaign_options

Lists the email campaigns (mailings) in the account, optionally filtered by campaign name, ID or email name. Use when the user asks which campaigns exist or refers to a campaign by name and its ID is needed.

list_campaigns

Lists the custom contact fields defined on one contact list (for example first_name) with their IDs. Use when the user asks what data the list stores, or when building segment or workflow criteria that reference list fields.

list_contact_fields

Lists the contact lists (mailing lists) in the account with their IDs and counts. Use when the user asks about their lists, or when another tool needs a list ID.

list_contact_lists

Lists the stored email messages (templates) on one contact list, optionally filtered by name. Use when the user asks which emails exist, or to find a message ID for a campaign or workflow.

list_email_messages

Lists the email message tags on a contact list, including global tags. Use when the user asks how emails are tagged, or to find a tag ID before tagging a new email message.

list_email_tags

Lists Ongage Events (trigger-based campaigns that send on a recurring schedule, e.g. monthly) on a contact list. Use when the user asks about their recurring or triggered campaigns, or to find an event's ID by name.

list_event_campaigns

Lists the segments on one contact list, including each segment's criteria. Use when the user asks which segments exist, or to resolve a segment name to its ID.

list_segments

Lists the sending connections (ESP connections, also called vendors) with their IDs, titles and ESP names. Use when the user asks which ESPs are connected, or when creating a campaign or email needs a connection ID.

list_sending_connections

Lists the Ongage system contact fields (ocx_*) with their IDs, titles and types, filtered to the set allowed for the chosen usage. Use when workflow criteria, webhook fields or contact-update values reference a system field; the IDs come from this tool and cannot be inferred.

list_system_contact_fields

Publishes, pauses or ends an automation workflow: live starts or resumes it, freeze pauses it, end archives it for good. Use when the user asks to publish, pause, resume or end an automation. Publishing checks that the workflow is complete; an ended workflow cannot be restarted.

update_workflow_status

Answers one plain-language question about email performance across all campaigns and automations (sends, opens, clicks, soft and hard bounces, complaints, CTR). Use when the user asks how their email is performing over a period. Covers the last 7 days unless the question names a period. Ask one short question per call (one metric set, one period); split multi-metric questions into several calls.

query_email_analytics

Restores a deleted automation workflow that was a draft or had ended when it was deleted. Use when the user asks to undo a workflow deletion. The restored workflow keeps its draft or ended status, so it does not run.

restore_workflow

Sends a stored email message now to the email addresses given, through one sending connection. Use when the user asks to send an email, or a test, to specific addresses they typed or confirmed. For a list or segment audience, use create_scheduled_campaign.

send_transactional_email

Stars or unstars an existing Contacts Activity report (the favorite flag in the Ongage UI). Use when the user asks to star, favorite or unstar a report. The flag is the only report property that can change.

set_contact_activity_report_favorite

Renames an automation workflow, changes its status, or replaces its node graph; the node list replaces the whole graph, so nodes left out are deleted. Use when the user asks to change an automation. Read it with get_workflow first, change only what was asked, send back the complete node list with the existing node IDs, then read it again with get_workflow. Status live publishes it and it starts sending.

update_workflow

Changes an existing segment's name, description or criteria; new criteria replace all existing rules. Use when the user asks to change how a saved segment is defined. Read its current definition with get_segment first and take field IDs from list_contact_fields and list_system_contact_fields. Campaigns and workflows that use the segment then target the new definition.

update_segment