Customer Event Data
This input is currently in beta. If you run into any issues, please reach out to product@monad.com.
Collects customer event data from DocuSign Monitor API for monitoring account activity and security events.
Sync Type: Incremental
Requirements
Before you connect Monad to DocuSign, you need an Integration Key, RSA Private Key, User ID, and Environment configuration.
-
Create a developer account and enable DocuSign Monitor (https://developers.docusign.com)
- Ensure your organization has the Monitor API enabled
-
Configure App Integration
- Log in to DocuSign and navigate to Integrations > Apps and Keys
- Click Add App and Integration Key
-
Set up your application
- App Name: Choose a descriptive name (e.g.,
Monad Connector) - General Info: Copy the Integration Key for later use
- Service Integration:
- Click Generate RSA to create an RSA Keypair
- Copy the Private Key (required for connector configuration)
- Additional Settings:
- Add Redirect URI:
https://app.monad.com/api
- Add Redirect URI:
- App Name: Choose a descriptive name (e.g.,
-
Grant Application Consent
- Replace the placeholders in the URL below:
<SUBDOMAIN>: Useaccountfor production oraccount-dfor development<INTEGRATION_KEY>: Use the Integration Key from step 3
- Navigate to this URL in a browser logged into your DocuSign developer account:
https://{SUBDOMAIN}.docusign.com/oauth/auth?response_type=code&client_id={INTEGRATION_KEY}&redirect_uri=https://app.monad.com/api&scope=signature%20impersonation- Once complete, ignore the 404 not found screen on the redirect. Docusign has recorded your consent, which is then attached to the app's integration key you created which will be used as a part of authentication for the input.
- Replace the placeholders in the URL below:
-
Obtain Your User ID
- Navigate to Organization > Users > Users
- Click View User on your admin account
- Copy the User ID for connector configuration
Details
Monad uses cursor-based pagination on the DocuSign Monitor API to incrementally fetch customer event data. The connector tracks the last processed event timestamp and cursor position to ensure no data is missed. On the first sync, if no backfill start time is specified, a full sync of available data is performed. All subsequent syncs are incremental.
Configuration
The following configuration defines the input parameters. Each field's specifications, such as type, requirements, and descriptions, are detailed below.
Settings
| Setting | Type | Required | Description |
|---|---|---|---|
| Environment | string | Yes | The DocuSign environment to connect to (development or production). |
| User ID | string | Yes | The user ID of the DocuSign admin account. |
| Backfill Start Time | string | No | The date to start fetching data from. If not specified, no past records will be fetched. |
Secrets
| Secret | Type | Required | Description |
|---|---|---|---|
| Integration Key | string | Yes | The integration key for the app in DocuSign, used to identify your application. |
| RSA Private Key | string | Yes | The RSA private key generated for the integration, used to securely authenticate API requests. |
Connector Limitations
-
Developer Account Required: A DocuSign Developer account is required to enable DocuSign Monitor.
-
Go-Live Process: DocuSign requires 20 development API calls before transitioning an app to live status in production. You can start with the
demoenvironment to make development calls, then update towwwonce the transition is complete. -
Data Retention: The DocuSign Monitor API only provides data from the last 7 days. Connectors that are paused or failing for more than 7 days will be unable to backfill data beyond that window.