Connected Accounts

When you add an application to an automation, Monkedo will request authorization. After you grant access, the account you connected will appear on the Connections page. This process ensures that Monkedo securely stores your credentials once, so you won’t need to re-enter your password every time an automation runs. The saved Connection is then used to authenticate all relevant components automatically.

Each connection:

• Belongs to a specific Monkedo user

• Is linked to a single external service

• Contains authentication details (OAuth tokens, API keys, credentials)

• Can be used by automations to perform actions

• Supports both private and shared (team) usage depending on visibility settings

When an automation runs, Monkedo uses the selected connection to authenticate the component that requires external access.

And if you delete the connection from the Connections page or change the permissions you granted, this will also affect the automation.

Connection Status

Each connection in Monkedo has one of three statuses:

• Active: The connection is valid and functioning correctly. Automations using this connection can run without issues.

• Invalid: The connection is no longer authorized. This may occur if the account credentials have changed, expired, or were revoked in the external application. The connection must be refreshed or reconnected.

• Unused: The connection has been created but is not currently linked to any automation. It is available for use but not yet active in a workflow.

Monkedo is designed with teams in mind. While team members share the same workspace, connections are private by default. Each user sees only their own connections on the Connections page. Team members cannot see or use each other’s connections unless explicitly shared.

Users have the option to change a private connection to Public. When a connection is Public:

• All team members can see it on the Connections page

• Any team member can select it inside an automation

• The automation can run using this shared account

This is useful when multiple people in the team must operate through the same external identity. So, only share accounts that are meant to be used commonly within the team, such as: Customer support teams often use a shared mailbox, dedicated Twitter bot account or service account, departmental accounts.