
Jotform
Your customers fill out forms and then ask about their submissions. Your AI agent pulls live data from Jotform, retrieves form details, checks submission history, and confirms account usage, all without anyone logging into the Jotform dashboard.




Your agent reaches into Jotform to pull user details, list forms, browse folders, and audit activity, turning static form data into dynamic conversation context.
Jotform
From submission tracking to account audits, see how AI transforms static form management into responsive, on-demand interactions.
A customer submits an application form and messages 'Did you get my submission?' Your AI Agent retrieves the user's forms list, identifies the relevant form by name, and confirms the most recent submission timestamp and total count. The customer gets immediate confirmation. Your team skips the login, search, and manual reply cycle that used to take five minutes per inquiry.
Your operations manager asks 'Are we close to our form limit this month?' Your AI Agent calls Jotform's user details endpoint, compares current form count and submission count against the plan limits, and flags if usage exceeds 80%. The team gets proactive alerts through conversation. No one discovers the problem after forms stop accepting responses.
During a quarterly audit, your compliance officer needs to know all form modifications in the past 30 days. Your AI Agent queries Jotform's user history endpoint filtered by action type 'formUpdate' and the date range, then delivers a timestamped log of every change. The audit gets completed in minutes instead of hours of manual export and review.

Jotform
FAQs
It depends on your Jotform account type. Standard accounts use api.jotform.com. European accounts use eu-api.jotform.com. HIPAA-compliant accounts use hipaa-api.jotform.com. Enter the correct domain during setup to ensure your agent connects to the right data center.
The current integration provides access to form listings, user details, folder structure, activity history, plan information, and account settings. For individual submission data, you can extend the agent's capabilities through Jotform webhooks that push submission data to Tars in real time.
Yes. The labels endpoint supports an owner parameter for workspaces and team accounts. Pass the workspace or team ID to retrieve form labels scoped to that specific workspace. Enterprise accounts also benefit from unlimited API calls per day.
When configured with the hipaa-api.jotform.com domain, all API requests route through Jotform's HIPAA-compliant infrastructure. Tars does not store form data between conversations, maintaining the compliance boundary. Consult your compliance team to verify your specific workflow meets requirements.
The agent inherits the permissions of the API key you provide. Generate a key from a Jotform account that only has access to specific forms or folders. Jotform's team and workspace features let you control which forms are visible to which API credentials.
The agent can filter history by actions including userCreation, formCreation, formUpdate, userLogin, userLogout, and apiKeyCreated. You can also specify date ranges using startDate and endDate parameters or predefined ranges like 'lastMonth' for quick lookups.
No. Tars queries Jotform in real time during active conversations. Form metadata, user details, and activity logs are fetched live and used only within the current session. Nothing is cached or replicated in Tars infrastructure after the conversation ends.
Embedding a form collects data passively. A Tars AI Agent actively converses with users, answers questions about existing submissions, checks account status, and navigates form structures on behalf of the user. It turns one-way data collection into a two-way interaction.
Don't limit your AI Agent to basic conversations. Watch how to configure and add powerful tools making your agent smarter and more functional.

Privacy & Security
At Tars, we take privacy and security very seriously. We are compliant with GDPR, ISO, SOC 2, and HIPAA.