Skip to content
leadflip
Sign inCreate your account

Request signature

2 min read

Builds the documents from your templates, sends the recipient a link, and files the signed PDFs into the fields you name. One signing session, any number of documents — whoever signs, signs all of them.

Step by step

  1. In the flow, choose the plus and pick “Request signature”.
  2. Under “Documents”, pick a template and the target field per row.
  3. The template needs a “Signature” element on it. Without one there is nowhere to sign.
  4. Check the recipient address — it defaults to the record's email field.
  5. Write subject and body. The mail adds the link as a button; it need not appear in the text.
  6. Pick a deadline. It starts when the mail goes out, not when the step is configured.

What happens if the automation runs twice?

Nothing doubles. If an open request over the same templates already exists, no second one is created — the deadline is extended. Whether a mail goes out again is up to the “Send again” switch.

The step says “nowhere to sign”. What is missing?

The chosen template carries no “Signature” element. The step refuses it rather than producing a document nobody can sign — the client would see a page without marks and still reach the end. The pencil next to the row opens the editor; drop a “Signature” element on the page and publish again.

Why is the target field empty before signing?

On purpose. If the unsigned draft were already there, “file exists” would be true for the whole waiting period — the automation would carry on as if signed, with a blank form in the field. Only completion writes into the target field.

The recipient printed and scanned it. Now what?

Put the scan into the same field by hand. The field means “signed copy on file” — regardless of route. A step waiting on the field carries on. What the record will not carry is proof: no protocol sheet, no event chain.

I corrected a first name while the request was open.

The generated PDF is frozen — the correction is not in it. The way out is to withdraw and request again. The signature box also stays where it was when the request was created, even if you have since rearranged the template.

Why is there no “Request signature” button on the record?

Because the record should sit where it sits in the process. A click you can do twice does not move it. When a request goes out is the automation's decision.