copy_email_message
ChatGPTCopies a stored email message (template) to one or more other contact lists. Use when the user wants the same email on another list. The original is unchanged and copying sends nothing.
Overview
Ongage Airis connects your Ongage email marketing account so you can ask questions about it in plain language and draft new assets without leaving the conversation. Ask how your campaigns, automation workflows and events are performing - sends, opens, clicks, bounces, complaints and click-through rate - and look up your contact lists, segments, email messages, tags and sending connections. Answers come from your own account data. Ask Airis to draft a campaign, an email message, a segment, a tag or an automation workflow. Everything it creates is saved as a draft inside Ongage, where you review, edit and publish it. Airis cannot send email, schedule or publish anything, or change or delete existing content. It acts with your own Ongage permissions through OAuth sign-in. Requires an Ongage account.
Tools
create_draft_campaign
ChatGPTCreates a new email campaign on a contact list as a draft, from an existing email message, segment and sending connection. Use when the user asks to set up a campaign. The draft is not scheduled or sent; the user reviews, schedules and sends it inside Ongage.
create_draft_workflow
ChatGPTCreates a new automation workflow as a draft, optionally with its nodes. Use when the user asks to build an automation. Read the node format from get_workflow_schema first and resolve referenced IDs with the list tools (list_email_messages, list_sending_connections, list_segments, list_contact_fields, list_system_contact_fields, list_behavioral_criteria_options, list_campaign_options). Placeholder node and socket IDs are replaced with generated UUIDs and the mapping is returned. The draft does not run until it is published with update_workflow_status.
create_email_message
ChatGPTSaves a new email message (template) with a subject and HTML content on a contact list. Use when the user asks to write or save an email. Saving it sends nothing.
create_email_tag
ChatGPTCreates a new email message tag and returns its ID for tagging new email messages. Use when the user wants to tag an email with a tag that list_email_tags does not return.
create_scheduled_campaign
ChatGPTCreates a new email campaign on a contact list and schedules it to send at a given time, from an existing email message, segment and sending connection. Use when the user asks to schedule or send a campaign and has confirmed the audience, email and send time. To save a campaign without scheduling it, use create_draft_campaign.
create_segment
ChatGPTCreates a new saved segment (a stored contact filter) on a contact list from criteria rules. Use when the user asks to define a new audience. Get field IDs for list-field rules from list_contact_fields first. Creating a segment sends nothing.
create_segment_from_report
ChatGPTCreates a new saved segment from a Contacts Activity report's filter conditions, as the report's Create Segment button in Ongage does, so the segment keeps matching future contacts. Use when the user asks for a segment based on a report. The segment holds active contacts only and does not carry the report's date range. Creating a segment sends nothing.
delete_contact_activity_report
ChatGPTDeletes a Contacts Activity report: it leaves list_contact_activity_reports and its download links stop working. Use when the user asks to delete a report. There is no restore.
delete_workflow
ChatGPTDeletes an automation workflow that is a draft or has ended; a live or paused workflow is ended first with update_workflow_status. Use when the user asks to delete an automation. restore_workflow brings it back.
duplicate_workflow
ChatGPTCopies 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.
edit_email_message
ChatGPTChanges 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.
get_account_info
ChatGPTReturns 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_campaign
ChatGPTReturns 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_contact_activity_schema
ChatGPTReturns 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_email_message
ChatGPTReturns 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_event_campaign
ChatGPTReturns 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_analytics
ChatGPTReturns 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_segment
ChatGPTReturns 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_workflow
ChatGPTReturns 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_analytics
ChatGPTReturns 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_schema
ChatGPTReturns 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.
list_behavioral_criteria_options
ChatGPTResolves 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_campaign_options
ChatGPTLists 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_campaigns
ChatGPTLists 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_contact_activity_reports
ChatGPTLists 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_fields
ChatGPTLists 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_lists
ChatGPTLists 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_email_messages
ChatGPTLists 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_tags
ChatGPTLists 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_event_campaigns
ChatGPTLists 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_segments
ChatGPTLists 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_sending_connections
ChatGPTLists 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_system_contact_fields
ChatGPTLists 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_workflows
ChatGPTLists 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.
onboarding_status
ChatGPTReports where setup of the signed-in user's Airis account stands: building (the brand book, then the first draft emails and drips) or ready, what was built, and the first step to take next. Use after start_onboarding, on the user's next message while it is building, and whenever the user asks whether setup is ready or what was built. You built this account from the user's website: answer those questions only from this tool, and never say you did not build it.
query_email_analytics
ChatGPTAnswers 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.
restore_workflow
ChatGPTRestores 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.
save_brand_details
ChatGPTSaves details of the user's brand into their Airis brand book, which every email Airis writes follows. Send only the fields the user just gave or agreed to (when you suggested the wording, only after they said it is right). Returns how complete the brand book is and what is still missing.
send_transactional_email
ChatGPTSends 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.
set_contact_activity_report_favorite
ChatGPTStars 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.
start_onboarding
ChatGPTCreates the signed-in user's Ongage Airis account from their business website: the workspace, its Ongage account, and a scan of the website that learns the brand and drafts the welcome emails. Use when the account is not set up yet; ask the user for the website first. Calling it again returns the same account and its progress. Building takes a few minutes: follow it with onboarding_status.
update_segment
ChatGPTChanges 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_workflow
ChatGPTRenames 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_status
ChatGPTPublishes, 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.
Capabilities
Writes
Example Prompts
Click any prompt to copy it.
