Docs
Search K

Appearance

Third-Party Accounts ​

Third-Party Accounts enable individual users to connect their personal credentials for external services. Unlike Service Accounts (which use centrally managed credentials), Third-Party Accounts require each user to sign in with their own account details to execute tasks on their behalf.

1. Overview ​

A Third-Party Account acts as a placeholder in the console for a specific external service (e.g., Autodesk, Google, GitHub). When a node requires user-level authentication, each designer must sign in with their own credentials to grant the node permission to perform actions in that service.

2. Configuring a Third-Party Account in the Console ​

  1. Navigate to the Console: Log in and select the Third-Party Accounts tab.

  2. Create a New Entry: Click New Third-Party Account, then:

    • Enter a Name (e.g., Autodesk-UserLogin).
    • Provide required details such as Client ID and Client Secret.
    • Add any additional configuration parameters specific to the service.

  3. Save: Click Create or Save. The account appears in the console but remains unsigned until a user completes sign-in.

Note: Configuring the application credentials here does not authenticate any user—it only registers the service for use in workflows.

3. Signing In Within a Node ​

When you insert a node that requires a Third-Party Account:

  1. Open the Configuration dialog for the node.

  2. In the Accounts dropdown, select the desired Third-Party Account placeholder.

  3. If you have not yet signed in, the account icon will be red, indicating authentication is needed.

  4. Click the red icon to open the Sign-In dialog:

    • Enter your personal credentials (username/password, OAuth flow, etc.).
    • Grant the necessary permissions when prompted.

  5. Upon successful sign-in, the icon turns green, and the node can execute with your credentials.

Tip: Once signed in, your credentials will be reused by any node in any workflow that references the same Third-Party Account.

4. Managing Session and Re-Authentication ​

  • Session Persistence: Your sign-in remains valid until the token expires or you explicitly sign out.
  • Re-Authentication: If a node fails due to expired credentials, you may be prompted to re-sign in the next time you run or edit the node.
  • Error Handling: Clear error messages will indicate if authentication has lapsed or if additional scopes are required.

5. Public Workflow Warning ​

If you include a Third-Party Account in a workflow that you mark as public, anyone with access to that public workflow may be able to execute it using your credentials. Ensure you trust the recipients before sharing workflows that utilize personal accounts.

Service your workflows with your own credentials—Third-Party Accounts ensure that actions requiring user-level access are executed securely and individually.

Tentech 2024