Integration
Connect Formstack Documents to Tomba
When something happens in Formstack Documents, your agent does the next thing in Tomba. 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 Formstack Documents and Tomba 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 Formstack Documents can start in Tomba
When New Merged Document in Formstack Documents
then Create Lead in Tomba
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 Formstack Documents and Tomba
Triggers and actions 1 trigger · 33 actions
- New Merged Document
Triggers when a merged/populated document is created.
- Combine Files
Joins several files into one PDF or Word document. Give it the files in the order you want them, either as links or as base64 content, and it returns the combined file.
- Convert File to PDF
Turns a Word, Excel, PowerPoint, image or HTML file into a PDF. Point it at the file with a link or supply the file content, and it returns the PDF.
- Copy Document
Makes a copy of one of your Formstack Documents templates under a new name, and returns the new document with its merge key, merge URL and available merge fields.
- Create Data Route
Creates a data route in Formstack Documents — a single endpoint that sends one set of data to several documents at once, following the rules you give it. Returns the new route with the URL to post data to.
- Create Data Route Merge
Sends one set of data into a Formstack Documents data route, which merges it into every document the route's rules select. Optionally returns the finished documents in the response.
- Create Document
Creates a new document template in Formstack Documents from HTML or from an uploaded PDF, Word, Excel or PowerPoint file, and returns its merge URL and the merge fields found in it.
- Delete Data Route
Deletes a data route from Formstack Documents. The documents the route pointed at are not deleted.
- Delete Document
Deletes a document template from Formstack Documents.
- Get Data Route
Returns one Formstack Documents data route, with its name, its merge URL and the rules that decide which documents the data goes to.
- Get Document
Returns one document template from Formstack Documents, with its name, type, output format, merge URL and — for HTML templates — the template's HTML.
- Get Document Fields
Returns the merge fields found in a Formstack Documents template, so you know which names to send when merging data into it.
- List Data Routes
Returns your Formstack Documents data routes, each with its name, key and the URL to send data to.
- List Documents
Returns your Formstack Documents templates, each with its name, type, output format and merge URL.
- Update Data Route
Updates a Formstack Documents data route — its name, folder, or the rules that decide which documents receive the data. Anything you leave blank stays as it is.
- Update Document
Updates a Formstack Documents template — its name, folder, output format, filename or the template content itself. Anything you leave blank stays as it is; the template type cannot be changed.
- Author Finder
Finds the most likely email address of an article's author from the article's URL.
- Check technologies
Detect the technologies (CMS, analytics, frameworks, hosting and more) used by a website domain.
- Count Email
Returns the number of email addresses Tomba has found for a domain, with breakdowns by type, department and seniority.
- Create Lead
Create a new lead . If the email already exists, fails with 422 status code.
- Detect email format
Detect the email address pattern used by a company domain.
- Domain Search
Finds the email addresses Tomba knows for a company, looked up by website domain or company name, along with details about the organization.
- Domain Status
Checks whether a domain is a webmail provider or a disposable email domain.
- Email Enrichment
Looks up the person and company details Tomba has for an email address, such as name, job title, company, location and social profiles.
- Email Verifier
Verify the deliverability of an email address.
- Enrich company
Look up company details (name, industry, location, social profiles, size, technologies) from a website domain.
- Find Email
Finds the most likely professional email address for a person from their name and a company domain or company name.
- Get employee locations
Get the breakdown of a company's employees by country, based on its domain name.
- Get Lead
Fetches a saved lead by ID, including its contact details, company, list, score, notes and custom attributes. An error occurs if the lead is not found.
- LinkedIn Finder
Enter a LinkedIn profile URL to find the associated email address.
- Phone Finder
Finds phone numbers for a contact from an email address, a company domain, or a LinkedIn profile URL.
- Phone Validator
Validate a phone number and get its carrier, line type, country and formatted versions.
- Reveal companies
Search Tomba's company database with a natural-language description or structured filters and return the matching companies.
- Similar Domains
Finds up to 25 companies and websites similar to a given domain.
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 Formstack Documents
Formstack Documents to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Formstack Documents to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Formstack Documents to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Formstack Documents to Google SheetsGoogle Sheets
Formstack Documents to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Formstack Documents to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Tomba
Questions
Formstack Documents and Tomba, answered
What can start an automation from Formstack Documents?
Any of Formstack Documents's 1 trigger in the catalog, including New Merged Document. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Tomba when something happens in Formstack Documents?
Any of Tomba's 18 actions, including Create Lead, Author Finder, Check technologies and Count Email. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Tomba to Formstack Documents?
Tomba has no triggers in the catalog today, so automations start in Formstack Documents. If you need the other direction, ask: your agent reads Tomba's API documentation and adds it.
Do I have to build a connector for Formstack Documents or Tomba?
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.