Integration
Connect DocuPipe and Process Street
When Document Processed fires in DocuPipe, your agent runs Create Data Set Record in Process Street, or Data Set Record Created in Process Street to Extract Data From Document in DocuPipe. 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 DocuPipe and Process Street 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 DocuPipe and Process Street can do together
From DocuPipe to Process Street
When Document Processed in DocuPipe
then Create Data Set Record in Process Street
When Document Processed in DocuPipe
then Update Data Set Record in Process Street
From Process Street to DocuPipe
When Data Set Record Created in Process Street
then Extract Data From Document in DocuPipe
When Data Set Record Updated in Process Street
then Upload and Extract Data in DocuPipe
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 DocuPipe and Process Street
Triggers and actions 8 triggers · 25 actions
Trigger
Document ProcessedTriggers when a document finishes parsing and OCR is complete.
Action
Add schemaCreates a new extraction schema in DocuPipe from a JSON schema you supply, and returns its schema ID.
Action
Analyze documentAsks DocuPipe a list of plain-language questions about one document and starts the analysis, returning the analysis ID to fetch the answers with.
Action
Classify DocumentSends one or more documents to DocuPipe to be sorted into your classes, and returns the job that is doing the work.
Action
Delete documentRemoves a document from your DocuPipe account.
Action
Delete schemaRemoves an extraction schema from your DocuPipe account.
Action
Extract Data From DocumentPulls structured data out of a document using one of your schemas, and returns the extraction to fetch the results with.
Action
Find documents by criteriaFinds documents in your DocuPipe account whose file name or document ID matches what you search for.
Action
Get DocumentReturns one document from your DocuPipe account, with its file details, processing status, parsed text and your own metadata.
Action
Get Extraction ResultReturns the data DocuPipe pulled out of a document, shaped by the schema that was used, along with per-field confidence details.
Action
Get schemaReturns one extraction schema from your DocuPipe account, including the JSON schema it applies and its guidelines.
Action
List documentsReturns the documents in your DocuPipe account, optionally narrowed to one dataset or a date range.
Action
List extractionsReturns the data extractions in your DocuPipe account, optionally narrowed to one schema, one document, or a specific set of extractions.
Action
List schemasReturns the extraction schemas in your DocuPipe account.
Action
Upload and Extract DataSends a file to DocuPipe and immediately starts pulling structured data out of it, returning both the new document and the extraction.
Action
Upload DocumentSends a file to DocuPipe to be read and turned into a document you can extract data from.
Trigger
Data Set Record CreatedTriggers when a new record is added to a data set.
Trigger
Data Set Record UpdatedTriggers when an existing record is updated in a data set.
Trigger
New CommentTriggers when a new comment is posted on a task in a workflow, or in a specific workflow run.
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
List Workflow Run Taskslists all tasks (id, name, status, dueDate) in one workflow run. Read-only; supplies the task id the Update Task action needs.
Action
List WorkflowsLists the workflows in your Process Street organization.
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.
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 DocuPipe
DocuPipe to PubloraPublish and schedule posts to ten social networks from one endpoint
DocuPipe to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
DocuPipe to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
DocuPipe to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
DocuPipe to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
DocuPipe to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into Process Street
HubSpot to Process StreetHubSpot is your all-in-one stop for all of your marketing software needs.
Google Calendar to Process StreetGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to Process StreetGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to Process StreetMailchimp marketing automation and email platform.
Pipedrive to Process StreetPipedrive is a sales CRM and pipeline management tool.
ActiveCampaign to Process StreetActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
DocuPipe and Process Street, answered
What can start an automation from DocuPipe?
Any of DocuPipe's 1 trigger in the catalog, including Document Processed. 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 DocuPipe?
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 DocuPipe?
Yes. When something happens in Process Street, your agent can act in DocuPipe too. This page covers both directions: Process Street's triggers and DocuPipe's actions are listed here as well.
Do I have to build a connector for DocuPipe 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 DocuPipe 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.