Integration
Connect ilert and Metaview
When New or Updated Incident fires in ilert, your agent runs Send sourcing message in Metaview, or New Conversation in Metaview to Find User on Call in ilert. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want ilert and Metaview to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What ilert and Metaview can do together
From ilert to Metaview
When New or Updated Incident in ilert
then Send sourcing message in Metaview
When New or Updated Incident in ilert
then Create AI field in Metaview
From Metaview to ilert
When New Conversation in Metaview
then Find User on Call in ilert
When New Conversation in Metaview
then Add Alert in ilert
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with ilert and Metaview
Triggers and actions 2 triggers · 43 actions
Trigger
New or Updated IncidentTriggers when an incident (alert) on the chosen ilert alert source is created or changes: assigned, escalated, accepted, raised, commented on, resolved, or a responder is added or removed.
Action
Accept IncidentAccepts a pending ilert alert (formerly called an incident) on behalf of the connected user, stopping its escalation, and returns the updated alert.
Action
Add AlertCreates an alert in ilert on the chosen alert source, which then escalates according to the source's escalation policy (or a policy or responders you specify).
Action
Add maintenance windowCreates a maintenance window in ilert that suppresses alerts for the chosen alert sources and services between a start and end time.
Action
Create IncidentCreates a new incident in ilert, optionally marking affected services and adding responders. Depending on the affected services, subscribers may be notified.
Action
Find User on CallFinds the user currently on call for an on-call schedule, along with the start and end of their current shift. Returns found=false when nobody is on call.
Action
Get alertReturns a single ilert alert by its id, including its summary, status, priority, alert source, escalation policy and responders.
Action
Get incidentReturns a single ilert incident by its id, including its status, severity, affected services and responders.
Action
Get maintenance windowFetches a maintenance window by ID. An error occurs if the maintenance window is not found.
Action
List Alert SourcesReturns all alert sources in your ilert account, including each source's integration type, integration key, status and escalation policy.
Action
List incidentsReturns the incidents in your ilert account, optionally filtered by status, affected service, severity and declaration date.
Action
List usersReturns the users in your ilert account, with their name, email, role and contact settings.
Action
Resolve IncidentResolves an ilert alert (formerly called an incident), closing it and stopping further escalation.
Trigger
New ConversationTriggers when a new conversation is available in Metaview.
Action
Build chartCreates a visual chart from conversation data with optional filtering, grouping, and timezone adjustment.
Action
Check enrichment statusReturns enrichment status and usage metrics for candidate data, with options to scope by person or enrichment type.
Action
Create AI fieldCreates a new AI-powered field that analyzes conversations to answer a custom question, with configurable value type.
Action
Create reportBuilds a report from conversations with filtering, metrics, grouping, and custom field inclusion.
Action
Fetch candidatesLooks up candidate information by ID, LinkedIn URL, email, or phone number in bulk.
Action
Find candidate's sequencesFinds which outreach sequences a candidate is enrolled in using their ID, LinkedIn URL, email, or phone.
Action
Get note templateReturns a note generation template by ID for use in automating note creation.
Action
Get search detailsRetrieves configuration and results for a sourcing search by ID.
Action
Get sourcing analyticsReturns sourcing analytics and metrics grouped by user, search, or date range with filtering options.
Action
Get sourcing messagesLists outreach messages sent in a sourcing search with pagination support.
Action
Get User ContextReturns information about the connected user account and available features.
Action
Give sourcing feedbackSubmits feedback on candidates from a sourcing search, optionally linking to the search that sourced them.
Action
Group conversationsGroups recorded conversations by a field (like recruiter, stage, or outcome) and returns counts and metrics per group.
Action
List application reviewsReturns a list of application reviews, optionally filtering by name or showing only active ones.
Action
List ATS jobsReturns ATS job postings, optionally filtered by job title.
Action
List ATS stagesReturns hiring pipeline stages for a job, or workspace-level stages if no job is specified.
Action
List available fieldsReturns available data fields for reports, optionally filtered by name.
Action
List candidates in sequenceReturns candidates enrolled in a sequence, with optional enrollment status and per-step delivery details.
Action
List field valuesReturns distinct values for a field across conversations, useful for building filters or dropdowns.
Action
List mailboxesReturns email mailboxes available in this Metaview workspace.
Action
List note template foldersReturns folders of note templates organized in the workspace.
Action
List note templatesReturns note templates available in the workspace, optionally filtered by name or with full section details.
Action
List sequencesReturns candidate sequences, optionally filtered by name, creator, or status; includes full configuration if requested.
Action
List sourcing candidatesReturns candidates from a specified sourcing search with optional filtering by pack, feedback status, and detail level.
Action
List sourcing searchesReturns all sourcing searches with optional pagination.
Action
Manage candidate sequenceAdds, pauses, resumes, cancels, removes, or updates candidate enrollments in a recruitment sequence.
Action
Manage note templateCreates, updates, or deletes call note templates with customizable sections for structured note-taking.
Action
Manage sequenceCreates, updates, duplicates, or deletes recruitment sequences.
Action
Search conversationsSearches call conversations with optional filtering, sorting, and field selection.
Action
Search reportsSearches reports by name, category, or ID with optional full configuration details.
Action
Send sourcing messageStarts or continues a sourcing or research search with a message to the AI agent.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from ilert
ilert to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
ilert to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
ilert to MailchimpMailchimp marketing automation and email platform.
ilert to StripeStripe is a payment processing platform for online businesses.
ilert to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
ilert to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Metaview
HubSpot to MetaviewHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to MetaviewGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to MetaviewGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Drive to MetaviewGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to MetaviewMailchimp marketing automation and email platform.
ActiveCampaign to MetaviewActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
ilert and Metaview, answered
What can start an automation from ilert?
Any of ilert's 1 trigger in the catalog, including New or Updated Incident. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Metaview when something happens in ilert?
Any of Metaview's 31 actions, including Create AI field, Create report, Send sourcing message and Build chart. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Metaview to ilert?
Yes. When something happens in Metaview, your agent can act in ilert too. This page covers both directions: Metaview's triggers and ilert's actions are listed here as well.
Do I have to build a connector for ilert or Metaview?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use ilert and Metaview without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.