❔Catch-up quick
Connect your account to natively supported third-party integrations with App Connections.
App Connections provide a pathway to leverage Workflows. Workflows are recipe-driven automations that connect your Forms and Form data to the rest of your business systems.
App Connections are third-party integrations that are natively supported within your account. When you connect your account to your existing third-party app accounts, you gain access to the connected app’s corresponding Workflows.
Your account is a stable foundation for a variety of integrations. But, App Connections are often easier to set up and manage than integrations like Webhooks and API connections.
If you have different accounts for a single integration, you can maintain each account as an independent connection. This provides a way to maintain separation between different parts of your organization.
Manage your connections in the web app. Access the App connections page in two ways - from your Workflow Dashboard, or through the user profile menu in the upper-right hand corner when you select Settings.
Your connections
As you add connections, you'll find them listed on the App Connections page under My connections. All of the available connections to which you have access are listed under Available connections.
🗒️ Note: Your available app connections depend upon your account tier. If you need access to an available integration, but it doesn’t appear under Available connections, contact your Account Manager.
Each connection displays a connection card. Within the connection card, you’ll find. . .
The app’s name.
An overview of what’s possible with the integration.
How many active connections you have with that integration.
Click the + Add Connection link on any connection card to begin the self-serve connection process.
Click the connection card for an existing connection, to navigate to a connection's overview page. Here, you’ll find and edit the connection’s name and activation status. You’ll also find the connection dates, and a link to the associated Workflows.
💡 As an example,
An energy company dispatches field workers in multiple regions out to inspect, repair, and maintain equipment. These teams may fill out multiple Forms at a single work site, including. . .
An equipment inspection
Preventative maintenance record
In order to maintain an audit trail, the company must keep copies of each Form.
With App Connections, this company connects their GoFormz account to their preferred cloud storage service (like Google Drive, Box, or Dropbox). They then set up their Workflow.
In this Workflow, the Northeast field inspection Template is selected. The Workflow is set to trigger when completed by all members of the Northeast field inspection Group.
After a PDF is generated, it’s then delivered to the specified folder.
Now, when a field worker completes their field inspection Form, it’ll dispatch directly to the appropriate folder in the company’s cloud storage account.
They’ll then repeat this process as necessary for the necessary Forms and Groups.
To do even more with these same Templates, they could then connect to their preferred database program - like Microsoft SQL - to to transfer data between GoFormz and their SQL database in real-time.
Best practices for your connections
App connections and their associated Workflows are features that users often cite as their biggest time-savers with their accounts. When you follow a couple of best practices, you’ll experience a high ROI on the time you invest.
Give your connections descriptive names
Of all best practices throughout your account, the use of clear and consistent naming conventions is the most valuable. When you name your connections, you’ll want to consider the credentials you use for the associated integration.
In order to keep track of the credentials used to set up a connection, you should include the username associated with the account within the connection’s name.
This is especially important if your integration has multiple connections.
Be aware - the name associated with the connection will display as the user who completed the associated action.
Monitor and manage them
As mentioned, you’ll find any connections you’ve already established listed on the web app’s App Connections page under My connections.
While connections are typically stable, sometimes they’ll require reconnection - typically as a matter of keeping your accounts secure.
The two most common times when you’ll need to reconnect are when you update the password associated with the connection, and when the refresh token with your third-party account expires.
If you need to temporarily deactivate a connection, access the appropriate connection card. You’ll then click the corresponding slider for the connection you need to suspend. Click it again when you’re ready to reactivate it.
Temporary connection pauses like this may be necessary if your organization’s data storage policies change, and you need to make the necessary updates.
Delete your connections as necessary. Once again, via the integration’s connection card, you’ll locate the appropriate connection and access the Actions menu (. . .) to find the Delete option.
Be aware - when you delete a connection, it’ll cause any associated Workflows to fail. So, you’ll need to manually update or delete any Workflows associated with that connection.
Related topics
While you can add a connection from the App Connections page, you can also add a new connection when you set up a Workflow.
If there’s a connection you’d like to add to your account that isn’t currently available, let us know.
Explore the other integration types available with your account.