Connect an application

to allow your {{scenario singular lowercase}} to get and receive data from third party services, you need to create a connection between make and those services connections allow your scenarios to perform actions like updating records in airtable, sending emails in gmail, adding rows in google sheets, and many more, from directly within your automated workflow in make since third party services use different technologies and authentication methods, the steps to create a connection in make can vary for some apps, you will only need to log in to the third party service and grant make permission to access your profile and data o ther apps may require you to enter specific credentials such as username and password, api key, client id, and client secret, or other values to prevent connection errors, always review the app's required connection details in our https //apps make com/ make offers two types of connections standard connections the most common type of connection, covered in detail in this article dynamic connections a variable that contains multiple connections you can choose from while executing the scenario learn more about this enterprise level feature https //help make com/dynamic connections if make doesn't offer an integration for the service you need, you can connect to it using the https //apps make com/http create a connection you create connections in the scenario builder when adding a module all users in your team in make can use and manage any connections you create in that team use your personal third party account and credentials carefully, especially when your team has otherusers if you're on the teams plan or higher, you may consider creating a separate team in which you are the only member to connect to make using your personal accounts and details to see how to connect a specific app, refer to the app's page in the https //apps make com/ these are the general steps to create a connection create a new scenario or open the existing one c lick the giant plus and search for the app and module you need in this example, we will choose dropbox > create a folder click create a connection steps 4 and 5 can vary for dropbox, you will only see the connection name field within the standard settings however, for other apps you may see additional optional and(or) mandatory fields related to authentication or module's requirements in the connection name field, you can name your connection for example, if you have two different dropbox accounts, you might name one "dropbox company" and the second "dropbox personal" click save a new window prompts you to grant make access to your data f ollow the on screen instructions to g rant make access to your dropbox account and data you have now created a connection between your dropbox account and make and can continue setting up the module you can reuse this connection in any other dropbox module across scenarios within your team, there can be multiple connections for the same app if a connection already exists, follow these steps to create another one click add in the connection field of the required app's module repeat the connection creation steps described above you can now select the required connection from the drop down menu in the connection field manage connections to view and manage your connections, click connections in the left sidebar and locate the required app from there, y ou can edit the connection verify the connection reauthorize the connection delete the connection you can also c lick the scenarios icon to see which scenarios are using the connection, and click the expand icon to open the scenario in a new tab click the permissions icon to view the permissions granted for that connection edit connections you can update the credentials and other details of a connection after you created it for example, if you need to change the api key, client id, client secret, required scopes, etc different apps will have different connection editing forms depending on the credentials or details they require and allow to edit editing a connection replaces the original data with the new data you have to provide all the credentials required to create the connection again, as make doesn't keep the original connection data to e dit a connection i n the left sidebar, c lick connections and locate the required connection click the three dots > edit for the required connection in the pop up window, enter the new details c lick save after you edit a connection, it will be automatically updated in all the modules that use it by e diting a connection, you update some of its details, but don't create a new one if you've switched accounts used in a connection, or the authentication method has been changed, you will need to create a new connection once you create it, follow the steps described https //help make com/replace connections across multiple modules to replace the old connection with a new one across multiple modules edit connections with api keys, oauth credentials, and scopes when updating credentials, especially for api key and oauth connections, make sure the new credentials include all necessary scopes to allow make modules to perform actions on your behalf this is particularly important if your scenario uses the make an api call module of the app make cannot ensure that the edited connection has the scopes required for all modules that use the connection if a module uses a connection with insufficient scopes, the {{scenario singular lowercase}} will end with an error to edit a connection with an api key click the three dots > edit for the required connection in the pop up window, fill in the new data in the form c onnection editing forms may vary depending on the app and on the type of credentials you can edit this is an example for the https //apps make com/openai gpt 3 connection click the save button to c onfirm changes if you click the close button, make closes the form and keeps your original connection make applies the saved changes immediately after confirming, make will update the connection details in all the modules where it's used to edit a connection with oauth credentials click the three dots > edit for the required connection in the pop up window, fill in the new data in the form c onnection editing forms may vary depending on the app and on the type of credentials you can edit this is an example of the https //apps make com/airtable click the save button to c onfirm changes if you click the close button, make closes the form and keeps your original connection follow the steps to confirm that make can access your account c heck the required fields to create the connection and review the connection scopes if everything is correct, confirm the connection update with the accept button make applies the saved changes immediately after confirming , make will update the connection details in all the modules where it's used verify connections to check whether your connection works properly , you can verify it to do that i n the left sidebar, c lick connections and locate the required app c lick verify the button briefly changes to verifying as make checks once the verification is completed, a green check mark appears if the verification fails, you'll see an exclamation mark this means that something is wrong with the connection to fix that, click reauthorize to update access to a third party service if it doesn't help, create a new connection reauthorize connections apps that use the oauth 2 0 protocol only grant access for a limited time in this case, you may need to reauthorize your connection periodically to reauthorize the oauth 2 0 connection i n the left sidebar, c lick connections and locate the required app c lick reauthorize and follow any on screen prompts that appear once the reauthorization is completed, a green check mark appears if the reauthorization fails, you'll see an exclamation mark this can happen when your browser blocks the reauthorization pop up, tokens have expired or been revoked, permissions changed, or there was a temporary outage try reauthorizing again if it doesn't help, delete the old connection and create a new one delete connections t o delete a connection i n the left sidebar, c lick connections and locate the required app click the three dots > delete for the connection you want to delete in a pop up window, click delete to confirm if the connection is used in any scenario, you'll see a corresponding warning and a list of scenarios where it's used click ok to confirm the deletion deleting a connection may cause your {{scenario plural lowercase}} to stop working be sure that the connection is not used in any scheduled or active {{scenario plural lowercase}} if there's a https //help make com/webhooks using the connection, you must first delete the webhook before you can delete the connection see also this article covers the basics to learn about advanced connection concepts and configurations, see the https //help make com/connections section in explore more