--- title: "Connect Formstack Documents to Okta - APIANT.ai" description: "When \"New Merged Document\" fires in Formstack Documents, your agent runs \"Add User to Group\" in Okta." canonical: "https://apiant.ai/connect/formstack-documents-to-okta" --- # Connect Formstack Documents to Okta When **New Merged Document** fires in [Formstack Documents](https://apiant.ai/connections/formstack-documents), your agent runs **Add User to Group** in [Okta](https://apiant.ai/connections/okta). Describe the whole flow and it is built, tested on every scenario and kept running. Formstack Documents **1** trigger Formstack Documents **15** actions Okta **22** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Formstack Documents and Okta 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 Formstack Documents can start in Okta - When **New Merged Document** in Formstack Documents then **Add User to Group** in Okta - When **New Merged Document** in Formstack Documents then **Create User** in Okta 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 Okta ## Triggers and actions 1 trigger · 37 actions - Trigger **New Merged Document** Triggers when a merged/populated document is created. - Action **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. - Action **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. - Action **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. - Action **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. - Action **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. - Action **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. - Action **Delete Data Route** Deletes a data route from Formstack Documents. The documents the route pointed at are not deleted. - Action **Delete Document** Deletes a document template from Formstack Documents. - Action **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. - Action **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. - Action **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. - Action **List Data Routes** Returns your Formstack Documents data routes, each with its name, key and the URL to send data to. - Action **List Documents** Returns your Formstack Documents templates, each with its name, type, output format and merge URL. - Action **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. - Action **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. - Action **Activate User** Activates a staged or deprovisioned Okta user and returns their activation link and token. Activation emails the user unless turned off. - Action **Add group** Creates a new Okta-managed group with a name, an optional description, and any custom group profile attributes defined in your org. - Action **Add User to Group** Adds an existing Okta user to an Okta-managed group. - Action **Assign user to application** Assigns an existing Okta user to an application, optionally setting their app username, password and app profile. Returns the resulting application user. - Action **Create User** Creates a new user in your Okta org, with or without credentials, and returns the new user's id and status. - Action **Deactivate User** Deactivates an Okta user, deprovisioning them from all assigned apps. This cannot be undone by the deactivation itself and may destroy the user's data in those apps. - Action **Delete group** Permanently deletes a group from your Okta org by its ID. - Action **Delete user** Permanently deletes a deactivated Okta user. If the user is still active, this deactivates them instead, and running it a second time deletes them. - Action **Find Group by Name** Returns the Okta groups whose name matches the name you specify, either exactly or by a partial match. - Action **Find User by Email** Returns the Okta users whose primary email matches the email you specify, including deprovisioned users. - Action **Get group** Returns one Okta group by its id, including its profile name, description and any custom attributes. - Action **Get user** Returns one Okta user, including their status, timestamps, credentials summary, and standard and custom profile attributes. An error occurs if the user is not found. - Action **List applications** Returns the applications in your Okta org, optionally narrowed by a name or label prefix or a filter expression. - Action **List group members** Returns the users who are members of an Okta group, with their profiles, including any custom attributes. Results can be narrowed with a search expression. - Action **List groups** Returns the groups in your Okta organization, optionally narrowed by a search, filter or name match. - Action **List users** Returns the users in your Okta organization, optionally narrowed by a search, filter or name query. - Action **Remove User From Group** Removes a user from a group managed directly in Okta. The user account itself is not changed. - Action **Reset user password** Starts a password reset for an Okta user and either emails them the reset link or returns the link. The user moves to Recovery status and can't sign in until they finish the reset. - Action **Suspend User** Suspends an active Okta user so they can't sign in, while keeping their group and app assignments. Suspended users can later be unsuspended or deactivated. - Action **Unsuspend user** Unsuspends a suspended Okta user and returns them to the Active state. - Action **Update group** Updates the name, description or custom attributes of an Okta-managed group. Anything left blank keeps its current value. - Action **Update user** Updates an existing Okta user's profile, including custom profile attributes, or credentials. Fields left blank keep their current values. ## Each app on its own - [ **Formstack Documents** Introducing Formstack Documents, formerly WebMerge.](https://apiant.ai/connections/formstack-documents) - [ **Okta** Okta helps companies manage and secure user authentication into modern applications, and for developers to...](https://apiant.ai/connections/okta) Reviews ## What our customers say ## More from Formstack Documents - [ **Formstack Documents to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/formstack-documents-to-hubspot) - [ **Formstack Documents to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/formstack-documents-to-salesforce) - [ **Formstack Documents to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/formstack-documents-to-slack) - [ **Formstack Documents to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/formstack-documents-to-google-sheets) - [ **Formstack Documents to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/formstack-documents-to-gmail) - [ **Formstack Documents to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/formstack-documents-to-google-calendar) ## More into Okta - [ **HubSpot to Okta** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-okta) - [ **Salesforce to Okta** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-okta) - [ **Slack to Okta** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-okta) - [ **Google Sheets to Okta** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-okta) - [ **Gmail to Okta** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-okta) - [ **Google Calendar to Okta** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-okta) Questions ## Formstack Documents and Okta, 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 Okta when something happens in Formstack Documents? Any of Okta's 22 actions, including Create User, Update group, Update user and Activate User. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Okta to Formstack Documents? Okta has no triggers in the catalog today, so automations start in Formstack Documents. If you need the other direction, ask: your agent reads Okta's API documentation and adds it. ### ### Do I have to build a connector for Formstack Documents or Okta? 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 Formstack Documents and Okta 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.