Connections in the Workflows Console show who created the connection but not the identity of the user/account used to Authorize the connection itself, whether for the Okta Connector or another third-party Connector. This can be useful for discovering which user/account is performing the API actions for the related cards that use the connection. The solution below demonstrates how the details for the identity can be discovered for Connectors with a supporting API endpoint to reach.

NOTE: Not all connectors will have the ability to perform this check even if the endpoint is available. Example:

• Custom API Action automatically prepends part of the URL, so the direct endpoint is not reachable:
  • Google Workspace can obtain this information via /v3/tokeninfo. However, the Google Workspace Custom API Action prepends /admin/directory to the Relative URL entered, so the GET would be against /admin/directory/v3/tokeninfo instead of /v3/tokeninfo. 

• Workflows Connectors
• Azure Active Directory Connector
• Excel Online connector
• Jira Connector
• Jira Service Management Connector
• Microsoft Teams Connector
• Office 365 Calendar Connector
• Office 365 Mail connector
• Okta Connector
• OneDrive Connector
• Salesforce Connector
• Slack Connector
• Other 3rd Party Connectors have an API endpoint that provides details for the user that made the API call, which can be reached by using a Read User or Customer API Action card (Vendor dependent)

1. Create a flow.
2. Add a card similar to the examples below. 
3. Run the flow or test the card.
4. Observe the data in the response to see the information for the account authorized for the selected connection.
5. After determining the account used, it is recommended to rename the Connection used to have the account name to easily identify it in the future.

The below list is not all-inclusive, and there may be other endpoints available. These are some known examples:
 

• Azure Active Directory connector
  • Card: Custom API Action Method=GET
  • Set Relative URL to /me
  • API Reference: GRAPH API User Get

• Excel Online connector
  • Card: Custom API Action Method=GET
  • Set Relative URL to /v1.0/me/drive
  • API Reference: GRAPH API - Get User's OneDrive (usable for Excel Online Connector)
  • NOTE: Information will be under the owner object in the response.

• Jira connector
  • Card: Custom API Action Method=GET
  • Set Relative URL to /rest/api/2/myself
  • API Reference: JIRA API Group Myself

• Jira Service Management connector
  • Card: Custom API Action Method=GET
  • Set Relative URL to /api/2/myself
  • API Reference: JIRA API Group Myself

• Microsoft Teams connector
  • Card: Custom API Action Method=GET
  • Set Relative URL to /me
  • API Reference: GRAPH API User Get

• Office 365 Calendar connector
  • Card: Custom API Action Method=GET
  • Set Relative URL to /me
  • API Reference: GRAPH API User Get

• Office 365 Mail connector
  • Card: Send Email
  • Set To to the desired email
  • NOTE: This sends an email to that address, and the sender of the email will be what the connection is Authorized with.

• Okta connector
  • Card: Read User
  • Set ID or Login to me 
  • API Reference: Get Current User

• OneDrive connector
  • Card: Custom API Action Method=GET
  • Set Relative URL to /me/drive
  • API Reference: GRAPH API - Get User's OneDrive 
  • NOTE: Information will be under the owner object in the response

• Salesforce Connector
  • Card: Custom API Action Method=GET
  • Set Relative URL to /services/oauth2/userinfo
  • API Reference: Query for User Information 

• Slack Connector
  • Card: Custom API Action Method=GET
  • Set Relative URL to /auth.test
  • API Reference: Slack auth.test
  • NOTE: Information will be under the owner object in the response.

Related References

• Credentials Used by Shared Connection in Okta Workflows
• How to Find Which Identity Deleted or Reauthorized a Connector/Connection from Workflows Console
• How to Authorize an Okta Connection in Okta Workflows