Integration
Connect Process Street to Netlify
When New Comment Attachment fires in Process Street, your agent runs Add build hook in Netlify. 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 Process Street and Netlify to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Process Street can start in Netlify
When New Comment Attachment in Process Street
then Add build hook in Netlify
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 Process Street and Netlify
Triggers and actions 4 triggers · 18 actions
- New Comment Attachment
Triggers when someone attaches a file to a comment in a workflow run.
- New Task Checked
Triggers when a task is checked off in a workflow.
- New Workflow Run
Triggers when a workflow is run.
- Task Ready
Triggers when a task is ready to be worked on.
- Create Data Set Record
Adds a new record to a data set.
- Delete Data Set Record
Deletes an existing record in a data set.
- Find Data Set Records
Search for data set records by form fields.
- Find Workflow Run
Search for a workflow run by ID, name, form fields, and other attributes.
- 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.
- Run Workflow
Runs a workflow.
- Update Data Set Record
Updates an existing record in a data set.
- Update Task
Update a task in a workflow run.
- Update Workflow Run
Update an existing workflow run.
- Add build hook
Creates a build hook on a Netlify site, returning the unique URL that triggers a new build when called.
- Add environment variable
Creates an environment variable on a Netlify team or on a single site.
- Add site
Creates a new Netlify site (project), optionally linked to a Git repository, and returns the created site.
- Delete site
Permanently deletes a Netlify site.
- Get build hook
Returns a build hook on a Netlify site, including its title, branch and trigger URL.
- Get site
Returns a Netlify site's details, including its URLs, domains, build settings and published deploy.
- List environment variables
Returns the environment variables for a Netlify team, or for one site in it, with their values, scopes and deploy contexts.
- List sites
Returns the sites (projects) in your Netlify account, optionally filtered by name or ownership.
- Update site
Updates a Netlify site's settings, such as its name, custom domain, password, build settings and HTTPS enforcement. Returns the updated site.
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 Process Street
Process Street to Google SheetsGoogle Sheets
Process Street to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Process Street to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Process Street to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Process Street to StripeStripe is a payment processing platform for online businesses.
Process Street to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Netlify
HubSpot to NetlifyHubSpot is your all-in-one stop for all of your marketing software needs.
Google Calendar to NetlifyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Process Street and Netlify, answered
What can start an automation from Process Street?
Any of Process Street's 4 triggers in the catalog, including New Comment Attachment, New Task Checked, New Workflow Run and Task Ready. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Netlify when something happens in Process Street?
Any of Netlify's 9 actions, including Update site, Add build hook, Add environment variable and Add site. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Netlify to Process Street?
Netlify has no triggers in the catalog today, so automations start in Process Street. If you need the other direction, ask: your agent reads Netlify's API documentation and adds it.
Do I have to build a connector for Process Street or Netlify?
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.
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.