Apps
Apps connect Studio Actions to external systems and to Dooap. Each app holds the configuration and credentials Studio needs to call a specific service, and it contributes triggers, inputs, and tools that Actions can use.
Tenant Admins manage apps from Tenant Admin > Apps. From here you can create new apps, configure credentials, and review the resources each app provides to Actions.
What an App Provides
Depending on its type, an app can contribute any combination of these resources to Actions in the tenant:
- Triggers start an Action when something happens in the external system, such as a new email or a new file.
- Inputs read data from the external system at the start of a step, such as the body of an email or the bytes of a file.
- Tools perform actions in the external system from inside an Agent step or a Tool Call step, such as sending an email, writing a file, or marking a message as read.
Some apps provide all three; others provide only tools.
Creating an App
- Go to Tenant Admin > Apps.
- Select New.
- Choose the app type that matches the external system you want to connect.
- Enter a clear, descriptive name, for example
Microsoft Exchange - Accounts PayableorAzure Storage - Invoice Drop. - Fill in any app-specific fields, such as a mailbox address or storage account name.
- Save the app.
- Open the saved app and select Configure Credentials to enter the secrets the app needs to authenticate.
You can create multiple apps of the same type. Each app is a separate connection with its own configuration and credentials, which lets you point different Actions at different mailboxes, storage accounts, or environments.
App Types
Studio supports the following app types. The first two are built into Studio. The remaining types are connector-style integrations with specific external services.
Dooap
Dooap apps connect Studio to a Dooap tenant and unlock Dooap-specific automation, such as invoice processing scenarios. They allow Actions to react to Dooap events and to read and act on Dooap data.
- Connects to: A Dooap tenant.
- Authentication: Service Principal (Client ID, Client Secret, Azure Tenant ID) plus the Dooap external tenant ID.
- Triggers: Yes. Each Dooap app exposes a Dooap event trigger that Actions can subscribe to.
- Inputs and Tools: Yes. Standard Dooap inputs and tools are available to Actions that use the app.
Use a Dooap app whenever an Action needs to interact with Dooap, for example to process invoices or respond to Dooap events.
To limit which Dooap events start an Action Flow, open its Filter. Besides the Company & Vendor Filters and the Invoice Status Filter, the last panel holds Filter Rules that inspect any field of the Dooap event payload with a JSON path. For example, the rule $.newAssigneeId Equals 11111111-1111-1111-1111-111111111111 starts the Action Flow on an ApproverChanged event only when the invoice is assigned to that user. An event must match every filter and every rule. Once the Action Flow has run, Pick from last run next to a rule's JSON Path shows the event payload of a recent run so you can click the field to filter on.
For the workflow events InvoiceSentToWorkflow, InvoiceReviewed, InvoiceApproved and WorkflowStepCompleted, the Next Workflow Step Filter starts the Action Flow only when the invoice's next workflow step matches one of its rules. Each rule picks step types (Review, Approve, AP) and, optionally, multiple users and user groups. Users are found by name or email, and user groups are listed per company. Switch Add assignees between User and User group to add both to the same rule; existing selections remain. Use the remove button on a selection to remove it. A next step must have a selected step type and be assigned to any selected user or group. No assignees selected means anyone. For example, an Approve rule selecting Anna and Approver group runs the Action Flow when an invoice reaches either Anna or that group for approval. Events that are not workflow events are not affected by these rules.
WorkflowStepCompleted is sent each time a user handles a review or approval step. Its Completed Workflow Step Filter works like the Next Workflow Step Filter but matches the step that was just handled: pick the step types (Review, Approve) and, optionally, the users and user groups the step was assigned to. For example, a Review rule selecting the Reviewers group runs the Action Flow each time a step assigned to Reviewers is reviewed. Use both filters together to react to a specific hand-over, such as a review by Reviewers that leaves an approval waiting for Approver group. Other events are not affected by the Completed Workflow Step Filter.
OpenAPI
OpenAPI apps let you bring an arbitrary HTTP API into Studio by importing its OpenAPI specification. Studio turns the spec into reusable inputs and tools that Actions can call without writing custom code.
- Connects to: Any HTTP API described by an OpenAPI specification.
- Authentication: None, API Key, or OAuth2 Client Credentials, depending on the target API.
- Triggers: Yes. Each OpenAPI app can expose a webhook trigger with a generated webhook URL, which external systems can call to start an Action.
- Inputs and Tools: Yes, and unique to this app type. You import inputs and tools from the OpenAPI specification, so the available operations match whatever the source API offers.
Use an OpenAPI app when you need to integrate a service that does not have a dedicated app type. See the OpenAPI app page for details on importing and configuring operations.
Azure Storage Account
Azure Storage Account apps connect Studio to an Azure Storage account so Actions can read, write, move, and delete files in Azure Blob Storage and Azure Files.
- Connects to: An Azure Storage account.
- Authentication: Service Principal, plus the storage account name.
- Triggers: Yes. New blob in container, and new file in file share.
- Inputs: Read a blob, read a file share file, and list the blobs or files in a folder.
- Tools: List, write, move, and delete blobs, and list, write, and move file share files.
Use an Azure Storage Account app to start Actions from files dropped in Azure storage, or to read and write files as part of an Action Flow.
To archive a blob to another storage account, connect an app for each account. In an Action Flow started by New blob in container on the source app:
- A Tool Call step uses Write_Blob on the archive app, with the source app's Read_Blob as its input, and sets
runtimeFiletolatest. Also setstorageAccountNameandcontainerNameon this step: by default they come from the trigger and point at the source. - A second Tool Call step uses Delete_Blob on the source app to delete the original. Without parameters it deletes the blob that started the run, and only the version the trigger detected. If a newer version was uploaded in the meantime, the delete fails and the newer version stays in place. With Detect modified or replaced blobs on, the trigger then starts a new run for it.
A failed step stops the run, so the original is deleted only after the archive copy has been written. This holds unless the Write_Blob step continues on error.
Wait for companion files
By default, the New blob in container and New file in file share triggers start one run for every new file. Some systems deliver one document as several files, for example an e-invoice as INV-1.xml plus its image INV-1.pdf. To start one run per document instead, enter the extensions in Companion Files > Wait for Extensions in the trigger settings, for example xml, pdf:
- Files in the same folder with the same name, differing only by these extensions, form a group. Letter case does not matter.
- The trigger holds back a group until a file exists for every extension, and then starts one run. Files that arrive in different polls are paired too. The first file never starts a run on its own.
- Files with other extensions are ignored. The name pattern must match every companion, so use
*or a pattern such asINV-*. - Stop Waiting After (minutes, optional) starts a run for an incomplete group when a companion is still missing after that time, with
isCompleteset to false. Leave it empty to wait until every companion arrives. - With Detect modified or replaced files on, a changed file in a group that already ran starts a run for the whole group again.
- Group by Name Pattern (optional) pairs companions whose names differ. See Companions with different names.
The run's triggerPayload describes the group:
- The usual file fields (
blobNameorfilePath,fileName,sizeBytes, and so on) describe the file with the first extension in the list. Read a blob and Read a file share file read that file by default. filesholds every file of the group by extension. To read the PDF, set the Read a blobblobNameto{{input.triggerPayload.files.pdf.blobName}}, or the Read a file share filefilePathto{{input.triggerPayload.files.pdf.filePath}}.- Delete_Blob without parameters deletes only that first file. Add a Delete_Blob step with
blobNameset to{{input.triggerPayload.files.pdf.blobName}}to delete the PDF too. groupNameis the shared name (INV-1), or the captured value (0012345678) when a group pattern is set.groupPathadds the folder (invoices/INV-1), andmissingExtensionslists what was still missing whenisCompleteis false.
When the Action Flow must not continue without every file, start it with a Filter Step on inputs.triggerPayload.isComplete.
Companions with different names
Some systems name the files of one document differently, for example Facture_0012345678.PDF and Facture_Details_0012345678_20260129_20261102180050.xml. Both names contain the invoice number, so enter a regular expression in Group by Name Pattern that captures it, for example Facture_(?:Details_)?(\d+):
- The pattern is matched against the file name, including its extension, and letter case does not matter.
- Files in the same folder that capture the same value form a group. The value comes from the group named
key, as in(?<key>\d+), otherwise from the first group in parentheses, otherwise from the whole match. Use(?:...)for parentheses that must not capture. - Files whose name does not match the pattern are ignored.
- When several files of one extension capture the same value, the newest one is used.
- Lookarounds and backreferences are not supported, and a pattern can be at most 500 characters long.
- An invalid pattern stops the trigger, and the trigger status shows the error.
List the files in a folder
List_Blobs and List_File_Share_Files return the files in one folder, for example the attachments stored next to the invoice that started the run. Both exist as an input and as a tool:
directoryPathis the folder to list. It defaults to the folder of the file that started the run. Use an empty value for the root.fileNamePatternkeeps the files whose name matches.*matches any characters and?one character, and letter case does not matter, for examplebar_200_attachment_*.pdf. It defaults to*.includeSubdirectoriesalso lists the files in subfolders. It defaults to false.topis the most files to return, from 1 to 1000. It defaults to 100. When more files match,truncatedis true.storageAccountNameandcontainerNameorfileShareNamedefault to the trigger, like Read a blob does.
The result has count, truncated, and a list of files: blobs with blobName, fileName, directoryPath, sizeBytes, contentType, lastModifiedUtc, and etag, or files with filePath instead of blobName and no contentType. It holds names and properties only, not file content.
To read every listed blob:
- Add a Loop Over Step, assign the List_Blobs input to the Loop Over Step itself, set Array JSONPath to
inputs.List_Blobs.blobs, and set Batch size to 1. - Inside the Loop route, give a step the Read_Blob input with
blobNameset to{{inputs.loopData.0.blobName}}. For file shares, useinputs.List_File_Share_Files.filesand the Read_File_Share_FilefilePath{{inputs.loopData.0.filePath}}.
As a tool, an Agent Step can call List_Blobs to find files by itself.
The list holds only the files that exist when the step runs. A file that arrives later is not in it. With companion files, leave extra files such as numbered attachments out of the group, because a group holds one file per extension, and list them in the Action Flow instead.
Microsoft Exchange
Microsoft Exchange apps connect Studio to Exchange Online through Microsoft Graph. They support inbound email scenarios as well as outbound email and message follow-up.
- Connects to: Exchange Online mailboxes through Microsoft Graph.
- Authentication: Service Principal with Microsoft Graph application permissions, plus a default mailbox address.
- Triggers: Yes. New email arrived, with filters for sender, subject, and body.
- Inputs: Read email details, list attachments, and read a selected attachment.
- Tools: Send email, archive email, mark email as read, flag email, and the same email-reading operations as inputs.
Use a Microsoft Exchange app for any Action Flow that reacts to incoming mailbox messages or sends email from an Exchange mailbox. For end-to-end examples, see Use Cases > Email in Actions.
A Microsoft Exchange app can also send the tenant's Human Task emails from your own mailbox. While it does, it cannot be deleted, disabled, or have its credentials removed, but its credentials can still be updated. See Tenant Admin: Human Tasks.
Azure Communication Services
Azure Communication Services apps connect Studio to Azure Communication Services for outbound email and SMS.
- Connects to: Azure Communication Services Email and SMS.
- Authentication: Connection String from the Azure Communication Services resource.
- Triggers: None.
- Inputs: None.
- Tools: Send email from a verified ACS Email sender, and send SMS.
Use an Azure Communication Services app when an Action only needs to send notifications, and inbound processing is not required.
Remote MCP
Remote MCP apps connect Studio to a remote Model Context Protocol (MCP) server and make the tools it exposes available to Actions.
- Connects to: A remote MCP server over Streamable HTTP.
- Authentication: None, API Key, or interactive OAuth 2.1, depending on the target server.
- Triggers: None.
- Inputs: None.
- Tools: Yes, and unique to this app type. The available tools are whatever the connected MCP server exposes.
Use a Remote MCP app to bring an external MCP server's tools into Studio without building a dedicated app type. See the Remote MCP app page for details on connecting, authenticating, and discovering tools.
SFTP Server
SFTP Server apps connect Studio to an SFTP server so Actions can download, upload, list, move, and delete files exchanged with partners, banks, or legacy systems.
- Connects to: Any SFTP (SSH File Transfer Protocol) server, using a host, port, and root folder configured on the app.
- Authentication: Username & Password, or Username & SSH Private Key (PEM/OpenSSH, optional passphrase). An optional pinned host key fingerprint protects against server impersonation.
- Triggers: None. Pair it with a Scheduled or Manual trigger.
- Inputs: Read a file.
- Tools: Download, upload, list, move, and delete files. Downloads become runtime files that later steps can use. Files are limited to 25 MB.
Use an SFTP Server app to pick up files a partner drops on an SFTP server, or to deliver generated documents to one. See the SFTP Server app page for paths, limits, and host key pinning.
Managing Credentials
Credentials are stored on the app, not on individual Actions, steps, or prompts. To rotate or update secrets:
- Open the app from Tenant Admin > Apps.
- Select Configure Credentials.
- Update the values and save.
All Actions that use the app pick up the new credentials on the next run.
When credentials are configured, the Credentials panel shows the non-secret parts of what is stored so you can confirm which identity the app uses: the Client ID, Azure Tenant ID, and scope for a Service Principal, the Client ID, token endpoint, scope, and header names for OAuth2 Client Credentials, the header name for an API key, and the username for SFTP Server apps. Use the copy buttons next to the identifiers when comparing against an app registration. The dialog is prefilled with these values when you reconfigure, so rotating a secret does not require retyping them. Secret values (client secrets, API keys, connection strings, passwords, private keys) are never shown or sent to the browser.
Credential changes are recorded in the Audit Log — it logs when credentials are configured or removed and by whom, but never the secret values themselves.
Exporting and Importing Apps
You can export an App to JSON and import it into another tenant — for example to promote a connection from UAT to Production, or to share a reusable App configuration.
- To export, open the App and select Export App. The Export App dialog shows the App together with all of its Input Types and Tools as JSON. Select Copy to Clipboard.
- To import, select Import on the Apps list, paste the JSON, and select Import New App. Studio recreates the App with its Input Types and Tools, and rebuilds its triggers from the App type.
A few things to keep in mind:
- Credentials are never exported. After importing, open the App and select Configure Credentials to enter the secrets for the target tenant.
- If an App with the same name already exists, Studio asks whether to Add numbered suffix or Overwrite existing.
- Individual Tools and Input Types can also be exported and imported on their own, with the same conflict choices.
- Built-in Standard Apps cannot be exported or imported.
For an end-to-end example that promotes Apps and Actions together, see Promoting from UAT to Production.
Things to Know
- Each app type provides a fixed set of triggers, inputs, and tools, except OpenAPI, which is defined by the imported specification.
- App-level settings such as the Exchange mailbox address or Azure storage account name are defaults. Triggers, inputs, and tools can override them where it makes sense.
- Credentials should always be entered through the Configure Credentials dialog, not pasted into Action prompts or step parameters.
- Some app types, such as Azure Communication Services, are outbound-only and do not provide a trigger. Pair them with another app or a Manual, Scheduled, Dooap, or data-driven trigger.