---
title: "Connect Firebase / Firestore to Ashby - APIANT.ai"
description: "When \"New Document Within a Firestore Collection\" fires in Firebase / Firestore, your agent runs \"Create Candidate Note\" in Ashby."
canonical: "https://apiant.ai/connect/firebase-firestore-to-ashby"
---

# Connect Firebase / Firestore to Ashby

When **New Document Within a Firestore Collection** fires in [Firebase / Firestore](https://apiant.ai/connections/firebase-firestore), your agent runs **Create Candidate Note** in [Ashby](https://apiant.ai/connections/ashby). Describe the whole flow and it is built, tested on every scenario and kept running.

Firebase / Firestore **1** trigger Firebase / Firestore **6** actions Ashby **17** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Firebase / Firestore and Ashby to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One 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.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

Example flows

## What Firebase / Firestore can start in Ashby

- When **New Document Within a Firestore Collection** in Firebase / Firestore then **Create Candidate Note** in Ashby
- When **New Document Within a Firestore Collection** in Firebase / Firestore then **Add candidate tag** 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 Firebase / Firestore and Ashby

## Triggers and actions 1 trigger · 23 actions

- Trigger

**New Document Within a Firestore Collection**

Triggers when a new document is added to a Cloud Firestore collection.

- Action

**Create Cloud Firestore Document**

Creates a new document within a Cloud Firestore collection.

- Action

**Delete Cloud Firestore Document**

Deletes a Firestore document by its collection path and document ID.

- Action

**Find Cloud Firestore Document**

Finds a document using a Structured Query within a collection.

- Action

**Get Cloud Firestore Document**

Returns one Firestore document by its collection path and document ID.

- Action

**Run Cloud Firestore Query**

Returns the Firestore documents in a collection that match a field filter.

- Action

**Update Cloud Firestore Document**

Updates the given fields on an existing Firestore document.

- Action

**Add candidate tag**

Adds an existing tag to a candidate in Ashby and returns the updated candidate.

- Action

**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.

- Action

**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.

- Action

**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.

- Action

**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.

- Action

**Create Candidate**

Creates a new candidate in Ashby with their name, contact details, social profiles, location and source.

- Action

**Create Candidate Note**

Adds a note to a candidate's profile in Ashby, optionally as HTML, private, or with notifications to subscribed users.

- Action

**Find Candidate**

Returns up to 100 candidates whose email address and/or name match the values you supply.

- Action

**Find Job**

Returns up to 100 jobs whose title or requisition ID matches the text you search for.

- Action

**Find Job Consideration**

Returns the applications (candidates being considered) for a job in Ashby, optionally narrowed by application status and creation date.

- Action

**Find Opening**

Returns the openings whose identifier matches the one you supply, including each opening's state, jobs, locations, hiring team and custom fields.

- Action

**Get candidate**

Returns the full details of a single Ashby candidate, including contact info, tags, applications, files and custom field values.

- Action

**List departments**

Returns all departments and teams in your Ashby account, optionally including archived ones or only those changed since a previous sync.

- Action

**List locations**

Returns the office and remote locations set up in your Ashby account, optionally including archived locations and regions.

- Action

**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.

- Action

**Update job**

Updates an existing job in Ashby — its title, team, location, default interview plan, employment type or requisition id.

- Action

**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.

## Each app on its own

- [ **Firebase / Firestore** Firebase Realtime Database and Google Cloud Firestore are flexible databases that give you the ability to...](https://apiant.ai/connections/firebase-firestore)
- [ **Ashby** Ashby's all-in-one recruiting software consolidates your ATS, Analytics, Scheduling, and CRM.](https://apiant.ai/connections/ashby)

Reviews

## What our customers say

## More from Firebase / Firestore

- [ **Firebase / Firestore to Google Cloud Text-to-Speech** Cloud API that converts written text into natural-sounding spoken audio in multiple languages and voices.](https://apiant.ai/connect/firebase-firestore-to-google-cloud-text-to-speech)
- [ **Firebase / Firestore to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/firebase-firestore-to-hubspot)
- [ **Firebase / Firestore to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/firebase-firestore-to-salesforce)
- [ **Firebase / Firestore to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/firebase-firestore-to-slack)
- [ **Firebase / Firestore to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/firebase-firestore-to-google-sheets)
- [ **Firebase / Firestore to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/firebase-firestore-to-gmail)

## More into Ashby

- [ **HubSpot to Ashby** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-ashby)
- [ **Salesforce to Ashby** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-ashby)
- [ **Slack to Ashby** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-ashby)
- [ **Google Sheets to Ashby** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-ashby)
- [ **Gmail to Ashby** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-ashby)
- [ **Google Calendar to Ashby** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-ashby)

Questions

## Firebase / Firestore and Ashby, answered

###

### What can start an automation from Firebase / Firestore?

Any of Firebase / Firestore's 1 trigger in the catalog, including New Document Within a Firestore Collection. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Ashby when something happens in Firebase / Firestore?

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 Firebase / Firestore?

Ashby has no triggers in the catalog today, so automations start in Firebase / Firestore. 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 Firebase / Firestore 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 Firebase / Firestore 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.
