---
title: "Connect ilert and Process Street - APIANT.ai"
description: "When \"New or Updated Incident\" fires in ilert, your agent runs \"Create Data Set Record\" in Process Street."
canonical: "https://apiant.ai/connect/ilert-to-process-street"
---

# Connect ilert and Process Street

When **New or Updated Incident** fires in [ilert](https://apiant.ai/connections/ilert), your agent runs **Create Data Set Record** in [Process Street](https://apiant.ai/connections/process-street), or **Data Set Record Created** in Process Street to **Find User on Call** in ilert. Describe the whole flow and it is built, tested on every scenario and kept running.

ilert **1** trigger ilert **12** actions Process Street **7** triggers Process Street **10** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want ilert and Process Street to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One 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.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

Example flows

## What ilert and Process Street can do together

### From ilert to Process Street

- When **New or Updated Incident** in ilert then **Create Data Set Record** in Process Street
- When **New or Updated Incident** in ilert then **Update Data Set Record** in Process Street

### From Process Street to ilert

- When **Data Set Record Created** in Process Street then **Find User on Call** in ilert
- When **Data Set Record Updated** in Process Street 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 Process Street

## Triggers and actions 8 triggers · 22 actions

- Trigger

**New or Updated Incident**

Triggers 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 Incident**

Accepts a pending ilert alert (formerly called an incident) on behalf of the connected user, stopping its escalation, and returns the updated alert.

- Action

**Add Alert**

Creates 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 window**

Creates a maintenance window in ilert that suppresses alerts for the chosen alert sources and services between a start and end time.

- Action

**Create Incident**

Creates 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 Call**

Finds 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 alert**

Returns a single ilert alert by its id, including its summary, status, priority, alert source, escalation policy and responders.

- Action

**Get incident**

Returns a single ilert incident by its id, including its status, severity, affected services and responders.

- Action

**Get maintenance window**

Fetches a maintenance window by ID. An error occurs if the maintenance window is not found.

- Action

**List Alert Sources**

Returns all alert sources in your ilert account, including each source's integration type, integration key, status and escalation policy.

- Action

**List incidents**

Returns the incidents in your ilert account, optionally filtered by status, affected service, severity and declaration date.

- Action

**List users**

Returns the users in your ilert account, with their name, email, role and contact settings.

- Action

**Resolve Incident**

Resolves an ilert alert (formerly called an incident), closing it and stopping further escalation.

- Trigger

**Data Set Record Created**

Triggers when a new record is added to a data set.

- Trigger

**Data Set Record Updated**

Triggers when an existing record is updated in a data set.

- Trigger

**New Comment**

Triggers when a new comment is posted on a task in a workflow, or in a specific workflow run.

- Trigger

**New Comment Attachment**

Triggers when someone attaches a file to a comment in a workflow run.

- Trigger

**New Task Checked**

Triggers when a task is checked off in a workflow.

- Trigger

**New Workflow Run**

Triggers when a workflow is run.

- Trigger

**Task Ready**

Triggers when a task is ready to be worked on.

- Action

**Create Data Set Record**

Adds a new record to a data set.

- Action

**Delete Data Set Record**

Deletes an existing record in a data set.

- Action

**Find Data Set Records**

Search for data set records by form fields.

- Action

**Find Workflow Run**

Search for a workflow run by ID, name, form fields, and other attributes.

- Action

**List Workflow Run Tasks**

lists all tasks (id, name, status, dueDate) in one workflow run. Read-only; supplies the task id the Update Task action needs.

- Action

**List Workflows**

Lists the workflows in your Process Street organization.

- Action

**Run Workflow**

Runs a workflow.

- Action

**Update Data Set Record**

Updates an existing record in a data set.

- Action

**Update Task**

Update a task in a workflow run.

- Action

**Update Workflow Run**

Update an existing workflow run.

## Each app on its own

- [ **ilert** ilert is a platform for alerting, on-call management, and status pages.](https://apiant.ai/connections/ilert)
- [ **Process Street** Process Street is a Compliance Operations platform that lets non-technical teams create powerful, API-driven...](https://apiant.ai/connections/process-street)

Reviews

## What our customers say

## More from ilert

- [ **ilert to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/ilert-to-salesforce)
- [ **ilert to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/ilert-to-slack)
- [ **ilert to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/ilert-to-mailchimp)
- [ **ilert to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/ilert-to-stripe)
- [ **ilert to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/ilert-to-shopify)
- [ **ilert to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/ilert-to-quickbooks-online)

## More into Process Street

- [ **HubSpot to Process Street** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-process-street)
- [ **Google Calendar to Process Street** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-process-street)
- [ **Google Drive to Process Street** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-process-street)
- [ **Mailchimp to Process Street** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-process-street)
- [ **Pipedrive to Process Street** Pipedrive is a sales CRM and pipeline management tool.](https://apiant.ai/connect/pipedrive-to-process-street)
- [ **ActiveCampaign to Process Street** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-process-street)

Questions

## ilert and Process Street, 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 Process Street when something happens in ilert?

Any of Process Street's 10 actions, including Create Data Set Record, Update Data Set Record, Update Task and Update Workflow Run. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Process Street to ilert?

Yes. When something happens in Process Street, your agent can act in ilert too. This page covers both directions: Process Street's triggers and ilert's actions are listed here as well.

###

### Do I have to build a connector for ilert or Process Street?

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 Process Street 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.
