Integration
Connect Divalto weavy and ilert
When New Record fires in Divalto weavy, your agent runs Find User on Call in ilert, or New or Updated Incident in ilert to Create Record in Divalto weavy. 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 Divalto weavy and ilert 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Divalto weavy and ilert can do together
From Divalto weavy to ilert
When New Record in Divalto weavy
then Find User on Call in ilert
When New Record in Divalto weavy
then Add Alert in ilert
From ilert to Divalto weavy
When New or Updated Incident in ilert
then Create Record in Divalto weavy
When New or Updated Incident in ilert
then Update Record in Divalto weavy
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 Divalto weavy and ilert
Triggers and actions 2 triggers · 24 actions
Trigger
New RecordTriggers when a new record is added to a CRM entity, such as a new customer.
Action
Create RecordCreates a record in a CRM entity, such as a customer or product, from a set of field values.
Action
Delete RecordDeletes a CRM record, either permanently or by marking it deleted.
Action
Get Entity DefinitionReturns one CRM entity's fields with their types and lengths.
Action
Get RecordReturns one record of a CRM entity by its record code.
Action
Import RecordsCreates or updates a batch of records of one entity in a single all-or-nothing import.
Action
List EntitiesReturns the CRM entities (tables) the API user can access, with their translated names.
Action
List RecordsReturns up to 1000 records of a CRM entity, such as customers or products.
Action
List View RecordsReturns up to 1000 rows of a CRM view.
Action
Mark Records ExportedSets the export status on records you already read, so they are not exported again until they change.
Action
Merge RecordsMerges a source record into a target record: linked records move to the target and the source is deleted.
Action
Search RecordsFinds records of a CRM entity whose field matches a value, returning the fields you choose.
Action
Update RecordUpdates fields on an existing CRM record; fields you leave out are not changed.
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.
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 Divalto weavy
Divalto weavy to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Divalto weavy to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Divalto weavy to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Divalto weavy to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Divalto weavy to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Divalto weavy to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into ilert
HubSpot to ilertHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to ilertGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to ilertGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ilertGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to ilertGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to ilertActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Divalto weavy and ilert, answered
What can start an automation from Divalto weavy?
Any of Divalto weavy's 1 trigger in the catalog, including New Record. Describe the moment in plain language and your agent picks the right one.
What can your agent do in ilert when something happens in Divalto weavy?
Any of ilert's 12 actions, including Create Incident, Accept Incident, Add Alert and Add maintenance window. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from ilert to Divalto weavy?
Yes. When something happens in ilert, your agent can act in Divalto weavy too. This page covers both directions: ilert's triggers and Divalto weavy's actions are listed here as well.
Do I have to build a connector for Divalto weavy or ilert?
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 Divalto weavy and ilert 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.