Integration
Connect Process Street to F1 API
When New Comment Attachment fires in Process Street, your agent runs Find drivers by name in F1 API. 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 F1 API 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 Process Street can start in F1 API
When New Comment Attachment in Process Street
then Find drivers by name in F1 API
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 F1 API
Triggers and actions 4 triggers · 21 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.
- Find drivers by name
Searches Formula 1 drivers by first name or surname and returns the matching drivers.
- Find teams by name
Finds Formula 1 teams whose name matches the search text.
- Get driver
Returns the details of one Formula 1 driver — name, nationality, birthday, racing number and short name.
- Get driver standings
Returns the drivers' championship standings for a season, with each driver's position, points, wins and team.
- Get team
Returns the details of a Formula 1 team, including its nationality, first appearance and championship counts.
- List circuits
Returns all Formula 1 circuits, both active and historic, with location, length and lap record details.
- List drivers
Returns all Formula 1 drivers in the database, both active and retired.
- List drivers by season
Returns every Formula 1 driver who took part in the given season, with their team.
- List races by season
Returns the races of a Formula 1 season, with schedule, circuit, winner and winning team for each race.
- List seasons
Returns the Formula 1 World Championship seasons, with each season's year, name and Wikipedia link.
- List teams
Returns all Formula 1 teams, active and historic, with their nationality and championship counts.
- List teams by season
Returns the Formula 1 teams that competed in a given season.
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 F1 API
Tally to F1 APIThe simplest way to create beautiful forms and surveys, for free.
HubSpot to F1 APIHubSpot is your all-in-one stop for all of your marketing software needs.
Questions
Process Street and F1 API, 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 F1 API when something happens in Process Street?
Any of F1 API's 12 actions, including Find drivers by name, Find teams by name, Get driver and Get driver standings. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from F1 API to Process Street?
F1 API has no triggers in the catalog today, so automations start in Process Street. If you need the other direction, ask: your agent reads F1 API's API documentation and adds it.
Do I have to build a connector for Process Street or F1 API?
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 Process Street and F1 API 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.