Integration
Connect Firebase / Firestore and thanks.io
When New Document Within a Firestore Collection fires in Firebase / Firestore, your agent runs Lookup Address by Email in thanks.io, or New Order in thanks.io to Create Cloud Firestore Document in Firebase / Firestore. 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 Firebase / Firestore and thanks.io 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 Firebase / Firestore and thanks.io can do together
From Firebase / Firestore to thanks.io
When New Document Within a Firestore Collection in Firebase / Firestore
then Lookup Address by Email in thanks.io
From thanks.io to Firebase / Firestore
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 thanks.io
Triggers and actions 4 triggers · 9 actions
- New Document Within a Firestore Collection
Triggers when a new document is added to a Cloud Firestore collection.
- Create Cloud Firestore Document
Creates a new document within a Cloud Firestore collection.
- Delete Cloud Firestore Document
Deletes a Firestore document by its collection path and document ID.
- Find Cloud Firestore Document
Finds a document using a Structured Query within a collection.
- Get Cloud Firestore Document
Returns one Firestore document by its collection path and document ID.
- Run Cloud Firestore Query
Returns the Firestore documents in a collection that match a field filter.
- Update Cloud Firestore Document
Updates the given fields on an existing Firestore document.
- Item Delivered
Triggers when a postcard, letter, notecard, or giftcard is delivered to a recipient.
- New Order
Fires once for each new order placed in your thanks.io account.
- QR Code Scan
Triggers when a QR Code on a postcard, letter, or notecard is scanned. This will also trigger when a giftcard is redeemed.
- Add Recipient
Adds a recipient to your account and to an optional list. Only US or Canadian addresses are accepted. If no/invalid address is specified and a valid email address is, we'll attempt to look up a valid street address using the email address for a fee.
- Delete Recipient
Deletes a Recipient from Mailing List.
- Lookup Address by Email
Returns the mailing address on file for a recipient in a thanks.io mailing list, looked up by their email address. Returns an empty list of matches when no recipient in that list has the email.
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 Firebase / Firestore
Firebase / Firestore to Google Cloud Text-to-SpeechCloud API that converts written text into natural-sounding spoken audio in multiple languages and voices.
Firebase / Firestore to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Firebase / Firestore to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Firebase / Firestore to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Firebase / Firestore to Google SheetsGoogle Sheets
Firebase / Firestore to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into thanks.io
Goaffpro to thanks.ioAffiliate marketing platform for ecommerce stores, managing affiliate recruiting, commissions, and referral...
Uploadcare to thanks.ioFile system as a service to handle your web and mobile app uploads.
Questions
Firebase / Firestore and thanks.io, 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 thanks.io when something happens in Firebase / Firestore?
Any of thanks.io's 3 actions, including Add Recipient, Lookup Address by Email and Delete Recipient. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from thanks.io to Firebase / Firestore?
Yes. When something happens in thanks.io, your agent can act in Firebase / Firestore too. This page covers both directions: thanks.io's triggers and Firebase / Firestore's actions are listed here as well.
Do I have to build a connector for Firebase / Firestore or thanks.io?
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 thanks.io 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.