FAQ: Simplified Agreement Automation

Hey Docusign community! We're excited to announce the newest enhancements to our Workflow Builder called Simplified Agreement Automation. These updates should make automating your agreement processes easier than ever

If you've ever spent your day routing contract requests, manually uploading signed PDFs into cloud storage folders, or waiting on IT just to build a renewal auto-notification, then this update is for you. We’ve built these features to take tedious admin tasks off your plate so you can focus on doing work that matters.

In this post, we’ll walk you through the changes and answer some common questions. If you have further questions or feedback, please leave a comment below!

What is "Simplified Agreement Automation"?

Think of it as giving everyone on your team the right tools to automate contract work without wrestling with complicated code or starting from an intimidating blank screen.

We're rolling out two new capabilities inside a brand-new Automations tab in Docusign IAM:

1. Rules: Quick, single-step "if this, then that" automations for common pre and post signature tasks.
2. Lookup Tables in Workflows: Spreadsheet-based decision tables that handle complex, multi-variable routing rules without messy branching logic.

What are Rules and when should I use one?

Rules are lightweight automations designed for quick, single-step background tasks. They use a simple "fill-in-the-blanks" setup:

Trigger (When this event happens) → Condition (under these conditions) → Action (Do this automatically)

Rules can be applied for both pre and post signature tasks, like routing contract requests, archiving signed agreements, renaming signed document files, or setting alert notifications for upcoming renewals.

Do I need to know how to code?

Nope! You don't need to know workflow architecture or how to write scripts, you just select options from drop-down menus.

If I’m in IT, will giving teams access to Rules cause governance headaches?

No, we built Rules with controlled self-service in mind so business teams get speed without bypassing guardrails:

• Role-based permissions: Account Admins control who can build. Non-admin users must be granted access to build or edit Rules.
• Approved integrations only: Users can only select account-level integrations that IT admins have already authorized.
• Built-in logic limits: Rules are deliberately capped at 5 simple conditions. If a process requires complex nested logic or branching, the system guides the user to full Workflow Builder governance.

By letting business users handle basic background tasks, IT teams get fewer routine support tickets while keeping full visibility and control over security.

What are some use-cases for Rules?

Here are a few ways our users are using Rules across the agreement lifecycle:

• Smart approvals: When a purchase request exceeds $100,000, automatically route an approval request to FP&A leadership.
• Instant team alerts: When an MSA request is created, post a notification in your team's Slack channel so the assigned attorney sees it right away.
• Automatic archiving: When an offer letter is signed, save the completed PDF directly to the right Google Drive or OneDrive folder.
• Proactive renewal tracking: When a contract is 90 days away from renewal, automatically open a renewal ticket in Agreement Desk so you never miss a deadline.
• Standardizing document naming: As soon as agreements are signed or archived, ensure that all agreements follow a consistent naming convention.

What are Lookup Tables, and how do they replace complex branching?

If you've ever built a workflow with dozens of If/Else branching steps just to route approvals by department, region, or contract value, you know how hard those workflows are to manage.

Lookup Tables separate your decision data from your workflow logic:

• Upload your data: You upload a spreadsheet (CSV or Excel) containing your business logic—like mapping Cost Center and Region to specific approver email addresses.
• Reference it in one step: In your workflow, you add a single step called Use Data from a Table.
• Dynamic lookups: When the workflow runs, it checks the table, finds the matching cost center and region, and grabs the right approver.
• Easy maintenance: When team members change or cost centers shift, you update the spreadsheet once. Every workflow connected to that table updates instantly without you having to touch the workflow canvas.

Companies with massive routing matrices—like Airbnb managing over 10,000 cost center approval combinations—use Lookup Tables to keep their processes clean and maintainable.

How do Rules compare to full Workflows?

Here is a quick look at when to pick a Rule versus building a full Workflow on the Maestro canvas:

Can I turn a Rule into a full Workflow if my process grows?

Yes! If a process starts as a single-step Rule and eventually needs additional steps like an intake webform or identity verification, then you don't have to start over.

On any published Rule, click Add additional automation. This opens your existing rule inside the full Workflow Builder canvas, converting your trigger and action into editable steps so you can expand your process naturally.

Which plans and regions get access to these features?

• Rules: Available to customers in the North America (NA) data center region across all Docusign IAM plans (English language).
• Lookup Tables: Globally available across all data center regions in 14 languages for accounts on premium IAM plans (IAM Professional and above).

How do I get started?

Getting started takes less than two minutes:

1. Log into Docusign IAM.
2. Click the Automations tab in the main navigation.
3. Head over to Rules to pick a pre-built template (like renewal alerts or Slack notifications) or click Add a Rule to build one from scratch.
4. Have a bigger process in mind? Click Workflows → Create Workflow and try describing your process in plain English!

We'd love to hear from you!

What routine contract tasks are you looking forward to automating first? Have questions about setting up your first Rule or Lookup Table? Drop your thoughts, questions, or use cases in the comments below!