Automate Agreement Tasks with Docusign Rules and Lookup Tables
Not every agreement task needs custom code. Learn how Docusign Rules and Lookup Tables help developers reduce custom integration work by automating routine tasks and simplifying routing logic in Workflow Builder.
For developers, time is often the biggest bottleneck. Requests like sending agreement notifications, routing documents, or updating another system can involve significant development work, from authentication and testing to deployment and maintenance. Individually, these tasks may seem small, but together they take time away from larger engineering priorities.
A new Automations tab in Docusign Intelligent Agreement Management (IAM) gives business teams more ways to handle routine tasks using capabilities such as Rules, Agents, and Workflow Builder with conditional logic. For example, Rules can automate renewal alerts, while Lookup Tables within Workflow Builder can help manage the reference data used for approval routing.
In this article, we'll look at how Rules and Lookup Tables work, when to use Rules versus Workflow Builder, and what these capabilities mean for developers.
What are Docusign Rules?
Docusign Rules automate routine agreement tasks using a simple pattern: Trigger → Condition → Action. The Rules Library provides no-code automation for tasks such as archiving agreements, routing requests, and triggering renewal alerts without requiring users to build a full workflow.
These are the kinds of requests that might otherwise end up in a developer's backlog. With Rules, business users can configure these automations themselves instead of relying on developers to build small custom integrations.
Rules use Workflow Builder under the hood, but serve a different purpose. While Rules are designed for single-step, personal, or team-specific productivity tasks, Workflow Builder supports more complex, multi-step orchestration.
To choose between these capabilities, consider the complexity of the task:
Use Rules for focused tasks with a trigger, condition, and action.
Use Workflow Builder for multi-step processes involving sequencing, branching, approvals, or multiple systems.
Involve developers when a process requires unsupported integrations, complex logic, custom services, organization-wide governance, or API-triggered workflows.
The Rules Library supports up to five condition statements using either all AND logic or all OR logic. Mixed or nested logic isn't supported, so tasks requiring more complex conditions are better suited to Workflow Builder.
For data governance, administrators can create Rules by default, while standard users need Workflow Builder access. Users can view and manage their own Rules, along with Rules shared with them, from the Rules homepage.
Availability: Rules are available in English only for accounts hosted in North American data centers, serving customers in the US and Brazil.
What is Docusign Workflow Builder?
Docusign Workflow Builder enables teams to automate end-to-end agreement workflows across the document lifecycle, connecting key agreement actions like document generation, routing, and conditional approvals without building every integration from scratch.
For developers, Workflow Builder is more than a visual configuration tool. It provides a programmatic abstraction layer for common automation patterns through the Workflow Builder API and tools like the Docusign MCP Server.
Instead of repeatedly implementing the same integration work, developers and solution teams can build on reusable workflow capabilities, supported integrations, and defined controls. Business builders can then configure, manage, and update agreement workflows within those boundaries without involving developers in every routine change.
What are Lookup Tables in Docusign Workflow Builder?
Lookup Tables let teams store and manage reference data separately from workflows. By maintaining this data in a CSV file and passing relevant inputs at runtime, teams can simplify workflow configuration and reduce duplicate logic.
Lookup Tables and branching (conditional routing) serve different purposes. Branching dictates the path a workflow takes based on specific criteria, while Lookup Tables retrieve reference data using key inputs. Together, they can simplify workflows by reducing duplicate mappings.
For example, teams can use Lookup Tables to maintain mappings such as:
Region and language → approver
Product tier → service-level agreement
Partner type → contract template
With reusable, versioned datasets, ownership and governance controls, change history, and fallback handling, Lookup Tables can reduce brittle branching, duplicated configuration, and custom services used primarily for routing logic.
For developers, this means less time building and maintaining custom routing logic when shared reference data can handle the task. Business builders can also update rules, routing paths, and lookup mappings as requirements change without relying on developers for every adjustment.
Availability: Lookup Tables are available worldwide in all supported languages for customers on IAM Professional plans or higher.
Rules vs. Workflow Builder: Which should you use?
Choose between Rules and Workflow Builder based on the task's complexity and whether custom development is required.
Capability | Best for | Logic & scope limits | Developer role |
|---|---|---|---|
Rules | Focused, repetitive tasks using triggers, conditions, and actions | Up to five condition statements; strictly all-AND or all-OR logic | Define platform boundaries and integrations; let business users self-serve |
Workflow Builder | Multi-step processes, conditional branching, approvals, and cross-system orchestration | Multi-system data flow, state management, and conditional branching | Build reusable custom step modules, maintain complex schemas, or trigger workflows via API |
Where Lookup Tables fit: Lookup Tables are part of Workflow Builder, rather than a separate automation tool. They help teams manage reusable reference data within workflows. Developers can use them to reduce duplicated branching, configuration, and custom services used primarily for routing logic.
Get started with Rules and Workflow Builder
Ready to try it? Sign in to your Docusign developer account to explore how Rules can automate common agreement tasks without custom code. Start with a simple agreement-completion notification, then explore Workflow Builder for more complex processes.
Before moving to production, consider the following:
Identify a low-risk backlog task. Choose a repetitive request with a clear trigger, limited data scope, and a reversible outcome.
Check the requirements. Confirm permissions, plan entitlements, approved integrations, and required approvals.
Simplify complex logic. Evaluate whether the new Lookup Tables feature can replace duplicated branching or custom lookup services with shared reference data.
Review the documentation. Verify availability, limitations, and supported configurations before deploying to production.
For more guidance, explore the below documentation for Rules, Workflow Builder, and Lookup Tables.
Resources
Ashlae Long is a software engineering manager at Docusign, focused on accessibility, usability, and simplifying the builder experience for Workflow Builder. Before being its manager, Ashlae was a senior engineer on the team. You can reach out to Ashlae on Linkedin.
Related posts
Docusign IAM is the agreement platform your business needs
