Wire DocRoute into your toolchain.

DocuSign

Setup steps

1. 1 In DocuSign Admin → Connect, create a new HTTP listener and note the Integration Key.
2. 2 In Apps and Keys, create a new App: type "Authorization Code Grant"; note the Client ID and Secret.
3. 3 In Salesforce → DocRoute → Setup → Integrations, choose DocuSign.
4. 4 Paste the Integration Key + Client ID + Secret. The setup wizard tests the OAuth handshake and confirms the connection.
5. 5 Configure the DocuSign Connect webhook URL — the setup screen displays the per-org Apex REST URL to paste.
6. 6 Map DocRoute envelope fields (signer roles, expiration, branding) to DocuSign envelope fields. Defaults work for most orgs.

Adobe Sign (Acrobat Sign)

Setup steps

1. 1 In Adobe Sign Admin → API → API Applications, create a new Application; note the Client ID and Client Secret.
2. 2 Configure the application's redirect URI to point at the DocRoute OAuth callback URL (shown in the setup screen).
3. 3 In Salesforce → DocRoute → Setup → Integrations, choose Adobe Sign.
4. 4 Paste your Adobe Sign API URL, Client ID, and Secret. Complete the OAuth flow when prompted.
5. 5 Configure the inbound webhook from Adobe Sign → API → Webhooks, pointing at the DocRoute Apex REST URL shown in the setup screen.
6. 6 Test with a sample envelope. Adobe Sign sends a status callback to DocRoute; the generation job updates automatically.

Generation entrypoints

DocRoute can be triggered from any of these — pick the one that fits your workflow.

• Quick Action on a record page. Drop the DocRoute · Generate Document quick action onto any object's record page. Reps click; DocRoute selects template, generates, saves to Files.
• Flow Builder. Use the DocRoute Generate Document invocable action inside any Flow — e.g., auto-generate a renewal contract when an Opportunity reaches a specific stage.
• Apex (programmatic). DocRoute.GenerationService.generate(recordId) returns a GenerationResult with the file ID, the chosen template, and any e-signature dispatch outcome.
• REST API. POST /services/apexrest/docroute/generate with a body containing the target record ID (and optional template override). Useful for cross-org triggers or external systems.

Custom PDF renderer adapter

The built-in renderer covers ~95% of cases. If you need specific fonts, layout behaviors, or you have a corporate-mandated PDF tool, implement the adapter interface:

1. 1Implement DocRoute.IRendererAdapter in your own Apex class — one method, renderHtmlToPdf(String html, RenderOptions opts).
2. 2Register your adapter in Setup → Renderers → New. DocRoute now routes all generation jobs through your adapter.
3. 3Optionally, configure renderer selection per template — e.g., use the built-in for internal docs and your custom adapter for customer-facing contracts.

Custom renderer adapter is included in Growth and Enterprise tiers.