Integration
Connect Process Street to BridgeDb
When something happens in Process Street, your agent does the next thing in BridgeDb. Describe it 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 BridgeDb 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 BridgeDb
When New Comment Attachment in Process Street
then Batch find equivalent identifiers in BridgeDb
When New Task Checked in Process Street
then Find equivalent identifier in target database in BridgeDb
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 BridgeDb
Triggers and actions 4 triggers · 14 actions
Trigger
New Comment AttachmentTriggers when someone attaches a file to a comment in a workflow run.
Trigger
New Task CheckedTriggers when a task is checked off in a workflow.
Trigger
New Workflow RunTriggers when a workflow is run.
Trigger
Task ReadyTriggers when a task is ready to be worked on.
Action
Create Data Set RecordAdds a new record to a data set.
Action
Delete Data Set RecordDeletes an existing record in a data set.
Action
Find Data Set RecordsSearch for data set records by form fields.
Action
Find Workflow RunSearch for a workflow run by ID, name, form fields, and other attributes.
Action
Run WorkflowRuns a workflow.
Action
Update Data Set RecordUpdates an existing record in a data set.
Action
Update TaskUpdate a task in a workflow run.
Action
Update Workflow RunUpdate an existing workflow run.
Action
Batch find equivalent identifiersMap many identifiers at once (newline-delimited, optional per-line source system code and optional target system code) to their equivalents, for a given organism.
Action
Find equivalent identifier in target databaseMap a source identifier to its equivalent identifier(s) in one specified target data source, for a given organism.
Action
Find equivalent identifiersMap a source identifier to all equivalent identifiers across every other data source, for a given organism.
Action
Find identifiers by nameFree-text search for identifiers matching a query string within an organism, optionally capped to a result limit.
Action
List data sourcesList the full BridgeDb data-source registry (system code, canonical name, identifier pattern, type) bundled with the deployment. Not organism-scoped.
Action
List organismsList the organisms loaded in this BridgeDb deployment, which are the valid values for the {organism} path segment used by every other operation.
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 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 Google SheetsGoogle Sheets
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 BridgeDb
HubSpot to BridgeDbHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to BridgeDbSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to BridgeDbSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to BridgeDbGoogle Sheets
Gmail to BridgeDbGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to BridgeDbGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Process Street and BridgeDb, 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 BridgeDb when something happens in Process Street?
Any of BridgeDb's 6 actions, including Batch find equivalent identifiers, Find equivalent identifier in target database, Find equivalent identifiers and Find identifiers by name. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from BridgeDb to Process Street?
BridgeDb has no triggers in the catalog today, so automations start in Process Street. If you need the other direction, ask: your agent reads BridgeDb's API documentation and adds it.
Do I have to build a connector for Process Street or BridgeDb?
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.