Open Integrations in your dashboard, find the service and check whether it supports the action you need.
Find and connect a service
Ask the builder to inspect the available actions before changing your app. A service listed in the catalog may not support every task or be enabled for every workspace.
When connecting, read the provider's consent screen. The requested permissions depend on that connector and account; they are not always limited to a folder or to read-only access. Check the connection status after completing consent, then test one small operation against the intended account.
To send through a connected mailbox, see Sending app email through Gmail.
Your workspace account or each visitor's account?
Overskill has both workspace connections and individual-user connections. Connecting your Google or social account to the workspace does not connect every visitor's account.
For a feature that uses each person's own account, ask the builder to use the supported user connection flow, require sign-in, and show which account is connected. Test with two separate users and verify that each sees only the intended outside account's data.
Connection selection matters: some integration calls can fall back to a workspace connection when there is no personal connection. If the feature must use only the visitor's account, have the builder refuse until that person's connection is ready rather than silently using yours. Revoke a connection and test that case too.
For a calendar example, see Choosing the Google Calendar account your app uses.
Reading Google Drive files
Check whether a Google Drive connection and the required read or export action are available to your account. Listing file names, downloading bytes, exporting a Google document and reading text from a PDF are different operations. Test the exact file type and permission with a file you own before using private customer documents.
A Drive share link is not a substitute for a connected account's authorization. If you only want to give the builder reference material, download and attach the file in builder chat instead; that does not require adding a Drive integration to the generated app.
Multiple connections and costs
Where multiple connections are available, give each a clear name and tell the builder which one the app should use. A successful connection is not permission to act in every account you have.
Builder work uses credits. Integration actions, additional AI processing and the outside provider can have their own charges. Verify the action and its cost before automating repeated work.
See Connecting an outside API if the built-in catalog does not offer the operation you need.