---
title: "How to Set Up Wrike E-Signature Automation"
description: "Configure a Wrike automation to automatically generate documents and send them for e-signature using TurboSign."
url: "https://docs.turbodocx.com/docs/Integrations/Wrike/signature-automation"
---

# How to Set Up Wrike E-Signature Automation

> Configure a Wrike automation to automatically generate documents and send them for e-signature using TurboSign.

## How to Setup E-Signature Automation

After [setting up your Wrike automation](https://docs.turbodocx.com/docs/Integrations/Wrike/setting-up-automation.md) with a trigger status and folder, follow these steps to configure it to generate documents and automatically send them for e-signature.

## Configure E-Signature Automation

### Step 1: Select Send for E-Signature

Click the **Send for e-signature** action card to select it as the automation action.

![Select E-Signature Action](https://docs.turbodocx.com/img/wrike-integration/SigAuto01-SelectESignature.jpeg)

### Step 2: Proceed to Signer Configuration

Click **Next** to continue to the signer configuration step.

![Click Next](https://docs.turbodocx.com/img/wrike-integration/SigAuto02-ClickNext.jpeg)

## Choose a Delivery Mode

Before configuring signers, choose **how** the automation delivers the document. This is the first section of the signature step, and it decides which of the sections below you need to fill in.

![The Delivery Mode section with the "Place signature fields manually" option highlighted](https://docs.turbodocx.com/img/wrike-integration/SigAuto-DeliveryMode.png)

| Mode | What happens when the automation fires | Anchor tags needed? |
|---|---|---|
| **Send for review first** | Posts a Wrike comment linking to the TurboDocx review page. You check the field placement, then click **Send** to deliver the signature emails. | Yes |
| **Send directly to signers** | Signature emails go out immediately. The Wrike comment confirms the request was sent. | Yes |
| **Place signature fields manually** | Posts a Wrike comment linking to the TurboDocx **field editor**. You drag the signature fields onto the document, then click **Send**. | **No** |

### When to use "Place signature fields manually"

Use it when your document has **no anchor tags** — the `{CustomerSignature}`-style placeholders that tell TurboDocx where each field goes.

The other two modes read those tags to position fields automatically, so a document without them can't be processed. That's common when the file is a scanned PDF, comes from a third party, or is a one-off contract nobody wants to template.

In this mode:

- The **Map Document Fields** section disappears — there is nothing to map, so no anchor tags are required.
- You still configure **recipients** below. The field editor needs to know who each field belongs to, so every recipient you add must have a Wrike email field — in this mode and in the other two.
- Nothing is sent to signers until you place the fields and press **Send** yourself. Even if the automation is also set to send directly, manual placement takes priority — a document with no fields would give signers nothing to sign.

Your existing field mappings are kept if you switch to this mode, so you can switch back without reconfiguring them.

:::tip Every recipient needs at least one field
In the field editor, **Send** stays disabled until *each* recipient has at least one field assigned to them. If you added three signers, place at least one field for all three — a signer with no fields has nothing to sign, so the editor won't let the document go out.
:::

## Configure Signers

:::note
The steps below apply to **all three** delivery modes. If you chose **Place signature fields manually**, complete this section and then skip ahead to [Reminders, Re-sends and Voiding](#reminders-re-sends-and-voiding-optional). The **Map Document Fields** steps won't appear.
:::

### Step 3: Select the First Recipient's Email Field

Select the Wrike field that contains the first recipient's email address. This field will be read from the Wrike task to determine who receives the signature request.

![Select Recipient Email](https://docs.turbodocx.com/img/wrike-integration/SigAuto03-RecipientEmail.jpeg)

### Step 4: Select the Recipient's Name Field (Optional)

Optionally, choose the field that represents the name of the recipient. This will be used in the signature request email.

![Select Recipient Name](https://docs.turbodocx.com/img/wrike-integration/SigAuto04-RecipientName.jpeg)

### Step 5: Add Additional Signers (Optional)

Optionally, add additional signers if your document requires multiple signatures.

![Add Additional Signers](https://docs.turbodocx.com/img/wrike-integration/SigAuto05-AddSigners.jpeg)

## Map Document Fields

### Step 6: Add a Document Field

Click **Add Field** to begin mapping document fields that the signer will need to fill out.

![Add Field](https://docs.turbodocx.com/img/wrike-integration/SigAuto06-AddField.jpeg)

### Step 7: Choose Document Fields

Click and choose the document field(s) that need to be completed by the signer.

![Choose Document Fields](https://docs.turbodocx.com/img/wrike-integration/SigAuto07-ChooseDocField.jpeg)

### Step 8: Select the Field Type

Select the specific field type for the document field (e.g., signature, date, text).

![Select Field Type](https://docs.turbodocx.com/img/wrike-integration/SigAuto08-ChooseDocField2.jpeg)

### Step 9: Set the Anchor Tag

Change the anchor tag to match the placeholder in your template (e.g., `{SalesSigner}`). This tells TurboSign where to place the field in the generated document.

![Set Anchor Tag](https://docs.turbodocx.com/img/wrike-integration/SigAuto09-ChangeAnchorTag.jpeg)

:::caution Anchor Tags Must Match Your Template
The anchor tag you set here **must exactly match** the corresponding variable in your document template. If they don't match, TurboSign won't be able to place the signature field. See [How to Add Signature Anchors](https://docs.turbodocx.com/docs/Integrations/Wrike/signature-anchors.md) for how to configure these in your template.
:::

**Optional: choose the alignment.** Under the anchor tag, **Alignment** sets where the signer's entry sits on the anchor: **Left**, **Center**, or **Right**. Pick **Left** when the anchor follows a label (like "Master's signature:") so every name starts at the same point. If you skip it, the field keeps its standard placement. Checkbox fields don't have this option.

![A signature field mapping card with the Alignment options highlighted](https://docs.turbodocx.com/img/wrike-integration/SigAuto-FieldAlignment.png)

On the last step of the wizard, the field mappings table shows your choice in its **Alignment** column (**Default** when you didn't pick one).

### Step 10: Map Additional Document Fields (Optional)

Optionally, repeat the process to map more document fields for the signer.

![Map More Fields](https://docs.turbodocx.com/img/wrike-integration/SigAuto10-MapMoreFields.jpeg)

## Reminders, Re-sends and Voiding (Optional)

Signature requests don't always go out right the first time. A signer misses the email, or someone spots a typo after the request was sent. The three settings below let your team handle that from Wrike by moving the task to a status, without opening TurboDocx.

All three are optional and sit below **Map Document Fields** in the signature step. Pick statuses your team doesn't already use to send for signature.

### Send a reminder

In **Send a reminder when the task moves to**, pick the Wrike status your team uses to nudge signers.

![The Send a reminder status picker highlighted, set to Please Sign](https://docs.turbodocx.com/img/wrike-integration/SigAuto-SendReminder.png)

When a task moves to that status, TurboDocx emails a reminder, with the same signing link, to every signer who hasn't signed yet. It doesn't create a new request, and requests that were voided are skipped. A comment on the task confirms how many signers were reminded.

### Void earlier requests when the task is sent again

Under **When the task is sent again**, check **Void outstanding requests when sending a new one** if a task should only ever have one open request.

![The "Void outstanding requests when sending a new one" option checked, with its warning and the Triggered by line](https://docs.turbodocx.com/img/wrike-integration/SigAuto-VoidOnSend.png)

With this on, each time the task moves to a send status and the new request goes out, TurboDocx voids every earlier request this automation sent from that task that isn't fully signed. The warning lists the statuses that trigger it on the **Triggered by** line.

:::caution Voiding can't be undone
Requests some signers have already signed are voided too, and their signers are emailed that the request was withdrawn. Fully signed requests are never touched. Leave the option off if earlier requests should stay open when the task is sent again.
:::

If the automation uses **Send for review first** or **Place signature fields manually**, earlier requests stay open until the new draft is sent. They're voided when someone sends it.

### Set a void status

In **Void status**, pick the Wrike status that withdraws a task's open requests, for example **Rejected** or **Needs Changes**.

![The Void status picker highlighted, set to Rejected](https://docs.turbodocx.com/img/wrike-integration/SigAuto-VoidStatus.png)

When a task moves to that status, TurboDocx voids the open signature requests this automation sent from the task. Signers who were sent a request are emailed that it was withdrawn, and one comment on the task says how many requests were voided. To send a corrected request, fix the task and move it back to the send status.

:::note Statuses can't overlap
The void status can't be one of the automation's trigger statuses, the reminder status, the completed status, or a status used in [Wrike Activity Updates](#wrike-activity-updates-optional). The wizard won't let you save an overlap, because one status move would then both send and void.
:::

On the last step of the wizard, **Trigger conditions** lists all three, so you can check them before you create the automation.

![The Trigger conditions summary highlighted, showing the Sends when, Reminds when and Voids when lines](https://docs.turbodocx.com/img/wrike-integration/SigAuto-ReviewVoidRules.png)

Each run shows up in the automation's **View Logs** with a summary such as "Voided the signature request" or "Sent a reminder to 1 signer who hasn't signed."

## Post-Signature Settings

### Step 11: Choose Where the Signed Document Gets Attached

Select where the signed document should be attached after all signatures are complete.

![Attach Signed Document](https://docs.turbodocx.com/img/wrike-integration/SigAuto11-AttachSignedDoc.jpeg)

### Step 12: Choose a Post-Signature Task Status (Optional)

Optionally, choose which status the triggering Wrike task should be changed to after the signature is completed.

![Choose Post-Signature Status](https://docs.turbodocx.com/img/wrike-integration/SigAuto12-ChooseStatus.jpeg)

### Step 13: Select the Completed Status

Select the status to apply (e.g., **Completed**) so your Wrike workflow advances automatically after signing.

![Select Completed Status](https://docs.turbodocx.com/img/wrike-integration/SigAuto13-SelectCompleted.jpeg)

### Step 14: Configure Notifications (Optional)

Optionally, choose who gets tagged or notified after a signature is completed.

![Configure Notifications](https://docs.turbodocx.com/img/wrike-integration/SigAuto14-Notifications.jpeg)

## Wrike Activity Updates (Optional)

Beyond the final **Completed** status you set above, you can have TurboDocx mirror **each step of the signature lifecycle** back into the triggering Wrike item — as a comment, a status change, or both. This keeps signer activity visible in Wrike in near real time, so downstream Wrike automations can react as a document moves through signing.

In the **Wrike activity updates** section of the signature action step, you'll see a row for each signature event. For every event you can independently:

- **Add a comment** — post a readable note on the Wrike task/folder when the event fires
- **Set a status** — change the Wrike item's custom status when the event fires (optional per row)

![Wrike activity updates section showing a comment toggle and status dropdown for each signature event](https://docs.turbodocx.com/img/wrike-integration/SigAuto-WrikeActivityUpdates.png)

### Supported events

| Row | Fires when | Notes |
|---|---|---|
| **Sent** | The document is dispatched to recipients | e.g. `Document sent for signature` |
| **Viewed** | A recipient opens the document for the first time | e.g. `Document viewed by John Doe` |
| **Signed** | An individual signer completes their signature | Posts per-signer progress like `1 of 2 signed` |
| **Progress** | A signer signs but the document is not yet fully complete | Document-level partial-signing progress |
| **Finalization failed** | The signed PDF could not be finalized (e.g. a signing error) | The document is **not** marked Completed |
| **Voided** | The signature request is voided or cancelled | e.g. `Document voided` |

These rows map to the same signature lifecycle events surfaced by [TurboSign webhooks](https://docs.turbodocx.com/docs/TurboSign/Webhooks.md) — see that page if you also want these events pushed to your own endpoints.

:::info The Completed row
The table also shows a **Completed** row, but it is not configured here — it reuses the post-signature status you set in **Step 12–13** above and posts automatically once all recipients have signed. Set the "all recipients signed" status there, not in this section.
:::

:::tip Comments and statuses are per event
Each row is independent. You can, for example, post a comment on **Viewed** and **Signed** but only change the Wrike status on **Voided** — leave any row's comment off and status unset to skip it entirely.
:::

### How it behaves

- **Comments are off by default.** A row only posts a comment if you turn it on, so existing automations don't suddenly start commenting when you save.
- **Per-recipient progress.** The **Signed** comment includes how many of the total signers have signed (`X of Y signed`) so multi-signer flows read in sequence.
- **Non-blocking.** Activity updates never interrupt the signature flow — if a Wrike comment or status change can't be applied, signing still completes and the event is logged.
- **Deleted status safety.** If a status you selected is later removed in Wrike, TurboDocx posts a warning comment instead of silently failing.

## Finalize the Automation

### Step 15: Proceed to Final Step

Click **Next** to advance to the automation creation step.

![Click Next](https://docs.turbodocx.com/img/wrike-integration/SigAuto15-ClickNext.jpeg)

### Step 16: Create the Automation

Click **Create Automation** to save and activate your e-signature automation workflow.

![Create Automation](https://docs.turbodocx.com/img/wrike-integration/SigAuto16-CreateAutomation.jpeg)

## What's Next?

- **[How to Add Signature Anchors](https://docs.turbodocx.com/docs/Integrations/Wrike/signature-anchors.md)** to your template if you haven't already
- **[How to Setup Static Field Mapping](https://docs.turbodocx.com/docs/Integrations/Wrike/field-mapping.md)** to template variables for static data
- If something isn't working, see [Troubleshooting and FAQ](https://docs.turbodocx.com/docs/Integrations/Wrike/troubleshooting.md)