Use DocuPotion blocks in Attio workflows

DocuPotion adds blocks to Attio's workflow builder so you can generate documents automatically and trigger workflows when a document is signed. There are two kinds of blocks: a step that generates a document as part of a workflow, and triggers that start a workflow the moment a document is sent for signature or fully signed. This article explains what each one does and how to wire them together.

  1. Before you start
  2. The blocks at a glance
  3. Generate a document as a workflow step
  4. Start a workflow when a document is signed or sent
  5. Using the Generate document step with e-signature
  6. Troubleshooting

Before you start

The blocks use the same connection as the rest of the DocuPotion app, so make sure DocuPotion is connected to your Attio workspace first. If you have already generated a document from a record, you are connected. If not, follow the Attio quickstart guide to install the app and connect both sides.

You also need at least one automation in DocuPotion (a template plus its field mapping for an Attio object). The Generate document step runs one of your automations, so build that first in DocuPotion's Automations tab.


The blocks at a glance

  • Generate document (a step): add it to any workflow to generate a document from one of your DocuPotion automations, using the record the workflow is running on.
  • Document sent for signature (a trigger): starts a workflow the moment a document goes out for e-signature.
  • Document signed (a trigger): starts a workflow the moment a document is fully signed by everyone.

You add these the same way as any Attio block. In the workflow builder, click to add a step or choose a trigger, and look for the DocuPotion blocks in the list.


Generate a document as a workflow step

The Generate document step generates a document in the middle of a workflow, for example when a deal reaches a certain stage. Add the step, then configure it:

  1. Choose the automation to run. This is one of your DocuPotion automations, and it decides which template is used and how record fields are mapped.
  2. Choose the record to generate from. By default this is the record the workflow is running on, and you can point it at a related record instead using a workflow variable.

When the step runs, the finished PDF document is attached to the record's files.


Outcomes: branch on what happened

The step finishes on exactly one outcome, and you can add steps after each one to branch your workflow. The outcomes depend on the automation you chose:

  • If the automation just generates a document, the outcomes are Generated and Failed.
  • If the automation sends the document for e-signature, the outcomes are Sent for signature and Failed.

Use the success outcome to continue (for example, update a field or post to Slack) and the Failed outcome to notify someone that generation did not complete.

One outcome fires, not both

The step always ends on a single outcome, so a step you place under Generated runs only when the document generated, and a step under Failed runs only when it did not. You never need to guess which path ran.


Start a workflow when a document is signed or sent

The two triggers let a document's progress start a workflow of its own. Choose Document sent for signature or Document signed as a workflow's trigger, then configure which documents it should listen for:

  1. Choose the object the documents belong to (deals, companies, people, or a custom object).
  2. Choose the automation: pick Any automation to fire for every document on that object, or a specific automation to fire only for that one.

When the trigger fires, you can update the record associated with the automation. For example, a Document signed workflow might move the deal to "Contract signed", create a task for onboarding, and send a Slack message with the signed file name.


Using the Generate document step with e-signature

If your automation sends for e-signature, the Generate document step finishes as soon as the signing request has gone out. Its success outcome is Sent for signature, not "signed". The step does not pause and wait for anyone to sign, because signing can take days.

To act after signing, use the Document signed trigger

If you want a workflow to do something once the document is actually signed (update a field, notify the team, kick off onboarding), do not put those steps after the Generate document step. Instead build a second workflow that uses the Document signed trigger. That workflow runs at the moment everyone has signed, however long that takes.

A typical two-workflow setup looks like this:

  1. Workflow 1 (triggered by a deal stage change): a Generate document step whose automation sends the contract for signature. Under Sent for signature, post an internal "contract sent" note.
  2. Workflow 2 (triggered by Document signed, filtered to that automation): move the deal to "Won", create the onboarding task, and message the account owner.

Troubleshooting

  • The automation you want is not in the step's list: the list shows the automations on the chosen object. Confirm the automation exists in DocuPotion and is set to the same object the workflow runs on.
  • A Document signed workflow is not firing: check the trigger's object and automation filter match the documents you expect, and that those documents are actually reaching the fully signed state. A document that is still awaiting a signer will not fire the signed trigger.
  • Nothing happens after "Sent for signature": that is expected. Use the Document signed trigger in a separate workflow to continue after signing (see the section above).

See also: Collect e-signatures from Attio records and the Attio quickstart guide.


Questions? Contact support@docupotion.com.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.