Integration
Connect Docparser and Text Request
When Parsed Document Data Available fires in Docparser, your agent runs Add group message in Text Request, or New Contact in Text Request to Upload Document in Docparser. 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 Docparser and Text Request 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 Docparser and Text Request can do together
From Docparser to Text Request
When Parsed Document Data Available in Docparser
then Add group message in Text Request
When Parsed Table Row Available in Docparser
then Send Message in Text Request
From Text Request to Docparser
When New Contact in Text Request
then Upload Document in Docparser
When New Message in Text Request
then Fetch Document From URL in Docparser
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 Docparser and Text Request
Triggers and actions 4 triggers · 25 actions
Trigger
Parsed Document Data AvailableTriggers whenever a new Document is processed and parsed data is available.
Trigger
Parsed Table Row AvailableTriggers whenever a new Document is processed and parsed table rows are available.
Action
Fetch Document From URLFetches a new document from a publicly accessible URL and imports it into Docparser to begin parsing. (To receive the parsing results, you'll need a separate Zap listening for the "New Parsed Data Available" Trigger).
Action
Upload DocumentUploads a new document to Docparser which will immediately begin parsing after reception. (To receive the parsing results, you'll need a separate Zap listening for the "New Parsed Data Available" Trigger).
Trigger
New ContactTriggers when a new contact is added to a dashboard.
Trigger
New MessageTriggers when a text message is sent or received on a dashboard.
Action
Add custom fieldCreates a new custom field on a Text Request dashboard, which can then be set on contacts.
Action
Add group messageSends a group text message to selected groups and/or phone numbers from a dashboard, immediately, at a scheduled time, or on a recurring schedule.
Action
Add keywordCreates a new keyword on a Text Request dashboard, with an optional automatic reply sent when a contact texts it.
Action
Add paymentSends a payment request text to a contact for the given amount and returns the new payment.
Action
Add userCreates a new user in your Text Request account with the given name, email and password, optionally granting administrator rights or dashboard permissions.
Action
Create GroupCreates a contact group on a dashboard.
Action
Create TagCreates a contact tag on a dashboard.
Action
Delete ContactDeletes a contact from a dashboard by their phone number.
Action
Delete groupDeletes a group from a dashboard. Contacts in the group are kept.
Action
Delete tagDeletes a contact tag from a Text Request dashboard. Contacts that carried the tag are not deleted.
Action
Find ContactsFinds contacts on a dashboard by name, phone number, tag or group.
Action
Get ContactReturns one contact on a dashboard by their phone number, including name, tags, groups, custom fields and message counts.
Action
Get dashboardReturns a dashboard (texting line) with its name, phone number and time zone.
Action
List custom fieldsReturns all custom fields defined for a Text Request dashboard (texting line), with each field's id and name.
Action
List DashboardsReturns every dashboard (texting phone line) in your Text Request account, with its ID, name and phone number.
Action
List GroupsReturns all contact groups on a dashboard.
Action
List keywordsReturns all keywords on a Text Request dashboard, with their auto-response, linked group and subscriber count.
Action
List messagesReturns the text messages sent and received on a Text Request dashboard, optionally filtered by date range.
Action
List scheduled messagesReturns the pending scheduled one-to-one messages for a dashboard, optionally filtered by send time or to recurring messages only.
Action
List tagsReturns all contact tags defined on a Text Request dashboard, with each tag's name and color.
Action
List usersReturns the users in your Text Request account, optionally filtered by email or external user ID.
Action
Send MessageSends a text message from a dashboard to a contact's phone number, now or at a scheduled time.
Action
Update groupRenames a group on a Text Request dashboard and updates its notes.
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 Docparser
Docparser to PrismixReal-time uptime for 77 AI APIs (OpenAI, Anthropic, Cursor, Gemini) — free JSON endpoint, no auth required
Docparser to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Docparser to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Docparser to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Docparser to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Docparser to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into Text Request
HubSpot to Text RequestHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Text RequestSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Text RequestSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Text RequestGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Text RequestGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Text RequestGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Docparser and Text Request, answered
What can start an automation from Docparser?
Any of Docparser's 2 triggers in the catalog, including Parsed Document Data Available and Parsed Table Row Available. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Text Request when something happens in Docparser?
Any of Text Request's 23 actions, including Create Group, Create Tag, Send Message and Update group. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Text Request to Docparser?
Yes. When something happens in Text Request, your agent can act in Docparser too. This page covers both directions: Text Request's triggers and Docparser's actions are listed here as well.
Do I have to build a connector for Docparser or Text Request?
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 Docparser and Text Request 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.