How credentials work across integration types
When you configure an integration through the Affinda Agent, there are two ways to connect to a downstream system: Pipedream-connected apps For apps in Pipedream’s library (Xero, Google Sheets, Outlook, SharePoint, and thousands of others), credentials are managed by Pipedream. You connect your account through Pipedream’s OAuth flow — Affinda never sees or stores your credentials for these connections. Pipedream processes API requests but does not store or log request payloads or response data. Manual pathway For any downstream system with an API endpoint, the Affinda Agent writes custom integration code that runs on Affinda’s platform. Use Secrets to store any API keys or credentials your integration needs to authenticate with the downstream system.Pipedream
The Affinda Agent uses Pipedream, a third-party platform, to offer thousands of integrations off the shelf. Pipedream handles the permissions and authentication required to export data from Affinda to other applications. To use Pipedream-connected apps, users will need to make an account with Pipedream — find their documentation here.Basic Configuration
Connected Account To create an integration, the user should first connect their account of their downstream application to Affinda using Pipedream. Users can create an integration that uses a single connected account or multiple. Workspace and document Type Integrations are tied to a specific workspace and document type. They will only execute on documents belonging to both those groups. Trigger Each integration requires a trigger; users can choose between document-parse completed or document validated.Agent
Users can describe their data export requirements in natural language, and the Affinda Agent will create the code required to complete the integration. Test run Once the integration code has been generated, the user can run a “test run” with existing documents to see if the integration behaves as expected. Integration Failed If your integration ran into an error, the “Fix in Chat” button passes the error message back to the agent to self-correct. Alternatively, you can view the run logs to manually review.Secrets
The Secrets section in integration settings lets you store API keys and credentials securely for use in integrations built on the manual pathway. Secrets are stored encrypted and are never visible after creation — not to you, and not to Affinda. Once saved, a secret’s value cannot be retrieved or displayed. If you need to update a credential, add a new secret with the same key name. Where to find it: Open an integration and go to the Settings tab. The Secrets section is listed below the trigger configuration. Secrets are injected as environment variables into your integration code and can be referenced using the key name you assigned (e.g.process.env.API_KEY).
Secrets apply to integrations built on the manual pathway only. For integrations using Pipedream-connected apps, credentials are managed by Pipedream and do not appear in this section.