Integration
Connect Process Street to Ashby
When Data Set Record Created fires in Process Street, your agent runs Create Candidate Note in Ashby. 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 Ashby 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 Ashby
When Data Set Record Created in Process Street
then Create Candidate Note in Ashby
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 Ashby
Triggers and actions 7 triggers · 27 actions
- Data Set Record Created
Triggers when a new record is added to a data set.
- Data Set Record Updated
Triggers when an existing record is updated in a data set.
- New Comment
Triggers when a new comment is posted on a task in a workflow, or in a specific workflow run.
- 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.
- List Workflows
Lists the workflows in your Process Street organization.
- 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 candidate tag
Adds an existing tag to a candidate in Ashby and returns the updated candidate.
- Add job
Creates a new job in Ashby with a title, department/team and location, optionally applying a job template, interview plan, employment type and brand.
- Add offer
Creates an offer for a candidate's application in Ashby by submitting the offer form for an offer process that has already been started.
- Change Job Consideration Stage
Moves a candidate's application (their consideration for a job) to a different interview stage, optionally with an archive reason and rejection email when archiving.
- Consider Candidate for Job
Considers a candidate for a job in Ashby by creating a new application, optionally placing it in a specific interview plan and stage with a source and credited user.
- Create Candidate
Creates a new candidate in Ashby with their name, contact details, social profiles, location and source.
- Create Candidate Note
Adds a note to a candidate's profile in Ashby, optionally as HTML, private, or with notifications to subscribed users.
- Find Candidate
Returns up to 100 candidates whose email address and/or name match the values you supply.
- Find Job
Returns up to 100 jobs whose title or requisition ID matches the text you search for.
- Find Job Consideration
Returns the applications (candidates being considered) for a job in Ashby, optionally narrowed by application status and creation date.
- Find Opening
Returns the openings whose identifier matches the one you supply, including each opening's state, jobs, locations, hiring team and custom fields.
- Get candidate
Returns the full details of a single Ashby candidate, including contact info, tags, applications, files and custom field values.
- List departments
Returns all departments and teams in your Ashby account, optionally including archived ones or only those changed since a previous sync.
- List locations
Returns the office and remote locations set up in your Ashby account, optionally including archived locations and regions.
- Update Candidate
Updates an existing candidate's name, contact details, social links, source, credited user and location in Ashby. Fields left blank are not changed.
- Update job
Updates an existing job in Ashby — its title, team, location, default interview plan, employment type or requisition id.
- Update Opening
Updates an existing opening in Ashby, such as its identifier, description, department, target dates, backfill flag or employment type. Returns the updated opening.
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 is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
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 Ashby
HubSpot to AshbyHubSpot is your all-in-one stop for all of your marketing software needs.
Google Calendar to AshbyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Process Street and Ashby, answered
What can start an automation from Process Street?
Any of Process Street's 7 triggers in the catalog, including Data Set Record Created, Data Set Record Updated, New Comment and New Comment Attachment. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Ashby when something happens in Process Street?
Any of Ashby's 17 actions, including Create Candidate, Create Candidate Note, Update Candidate and Update job. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Ashby to Process Street?
Ashby has no triggers in the catalog today, so automations start in Process Street. If you need the other direction, ask: your agent reads Ashby's API documentation and adds it.
Do I have to build a connector for Process Street or Ashby?
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 Ashby 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.