# Attio for Docusign IAM

> Connect Attio to your Docusign agreement workflows. Read people, companies, deals and custom objects to pre-fill agreements, create or update records, and file the signed document in the record's Files in Attio.

- Web page: https://fluidlabs.com/documentation/attio-for-docusign-iam
- Published by: Fluidlabs
- Status: Live on the Docusign App Center
- Docusign App Center listing: https://apps.docusign.com/app-center/app/7449d977-36a7-4aec-a6a7-796857719bb6
- App page: https://fluidlabs.com/integrations/attio-for-docusign-iam
- Last updated: 2026-10-09
- Support: docusign-support@fluidlabs.com

## Contents

- [Quick Start](https://fluidlabs.com/documentation/attio-for-docusign-iam#1-quick-start)
- [Implementation Guide & Known Behaviors](https://fluidlabs.com/documentation/attio-for-docusign-iam#2-implementation-guide--known-behaviors)
- [Installation and Configuration](https://fluidlabs.com/documentation/attio-for-docusign-iam#3-installation-and-configuration)
- [How to Use the App](https://fluidlabs.com/documentation/attio-for-docusign-iam#4-how-to-use-the-app)
- [Read from Attio](https://fluidlabs.com/documentation/attio-for-docusign-iam#5-read-from-attio)
- [Writeback to Attio](https://fluidlabs.com/documentation/attio-for-docusign-iam#6-writeback-to-attio)
- [File Upload to Attio](https://fluidlabs.com/documentation/attio-for-docusign-iam#7-file-upload-to-attio)
- [FAQ & Troubleshooting](https://fluidlabs.com/documentation/attio-for-docusign-iam#8-faq--troubleshooting)

---

## 1. Quick Start

### 1. Install the App

- Open the [**Docusign App Center**](https://apps.docusign.com/app-center/extensionapps) and search for **Attio**.
- Open the **Attio** app card, click **Install App**, then **Install and Authorize** on the consent screen.

### 2. Create a Connection

- On the installed app page, click **Connect Account**.
- Choose the connection visibility (**Private** or **Shared**), give the connection a name, and click **Log In**.
- Sign in to Attio if prompted, then click **Confirm** on the Attio access request.

### 3. Create a Workflow

- In Docusign, open **Workflow Manager** and create a workflow.
- Choose your preferred workflow start type.
- Add an Attio step: **Read from Attio**, **Writeback to Attio**, or **File Upload**.

### 4. Available Actions

- [**Read from Attio**](https://fluidlabs.com/documentation/attio-for-docusign-iam#5-read-from-attio): pull a person, company, deal or custom object record into your workflow to pre-fill an agreement.
- [**Writeback to Attio**](https://fluidlabs.com/documentation/attio-for-docusign-iam#6-writeback-to-attio): create or update a record.
- [**File Upload**](https://fluidlabs.com/documentation/attio-for-docusign-iam#7-file-upload-to-attio): file the signed document in the record's **Files**. In the step list it is named **File Upload** and carries the Attio logo.

### 5. Key Things to Know

- The app loads the objects and attributes of your Attio workspace when you connect. After you add or change objects or attributes in Attio, run **Reload Objects** on the connection.
- Every later step addresses a record by its **Record ID**, the long identifier Attio gives each record (for example `45c73e56-362d-4108-b8c2-460b632c4689`). The Read and Writeback steps return it.
- A Read step that finds no record does not stop the workflow. Its variables are empty.


## 2. Implementation Guide & Known Behaviors

The app works with every object in your Attio workspace: **People**, **Companies**, **Deals** and your custom objects. Attio's optional **Users** and **Workspaces** objects, lists and list entries, notes, tasks and comments are not available in workflow steps.

Field labels are the attribute names you see in Attio. Two kinds of attribute are split into parts:

| Attribute type | Fields in the step |
| --- | --- |
| Personal name (the **Name** of a person) | **Name: Full name**, **Name: First name**, **Name: Last name** |
| Location (such as **Primary location**) | **Primary location: Line 1** to **Line 4**, **Locality**, **Region**, **Postcode**, **Country code**, **Latitude**, **Longitude** |

Every object also has **Record ID**, which is read-only. Attributes Attio does not let you edit, such as **Created at**, **Created by** and interaction dates, can be read but not written.

### Building Workflows

- Find a record with a **Read from Attio** step, filtered by an attribute you know, such as **Email addresses** on People or **Domains** on Companies. Use the **Record ID** it returns in every later step: Writeback (Update) and File Upload (the subfolder). In the variable picker a field of the Read step is named after its object, for example **Person / Record ID**.
- The Writeback step returns the **Record ID** of the record it created or updated. Use it in a later File Upload step.
- A Read step that finds no record does not stop the workflow. Its variables are empty.

### Searching for a Record

- **Every field can be used in a rule**, including read-only fields and the parts of a name or a location.
- **Operator:** the rule editor offers **Equal to**.
- **AND and OR** can both be used in one rule. The rule editor lists conditions without parentheses; keep a rule to one connector, all AND or all OR, or check the result with **preview this step**.
- **Record ID** is used on its own in the rule. Combine other fields with AND or OR instead.
- **Linked-record fields** (such as **Company** on a person, **Associated company** on a deal) match the linked record's Record ID, a company's domain, a person's email address, or the record's exact name.
- **Workspace-member fields** (such as **Deal owner**, **Created by**) match the ID the field reads as; a read of any record shows it. A rule given as a member's email needs the Attio permission **User Management: read** on the connection; without it the step stops with a message naming the ID form. **Select**, **Status**, **Checkbox** and linked-record fields take **Equal to** and **Not equal to** only. A Record ID that does not exist returns nothing.
- **Several values in one rule.** On a field that holds several values (Email addresses, Phone numbers, Domains, a multi-select, linked people), `a; b` with **Equal to** means the record holds both. With **Not equal to** it matches a record that lacks either value; to find records that have neither, use two **Not equal to** rules joined by AND. On a field that holds one value, `a; b` stops the step.
- **Typed values.** A number, rating, checkbox or date-time rule takes a value of that kind; a date-time **Equal to** matches the whole unit you typed: a day for `2026-10-09`, a minute, a second or a millisecond for `2026-10-09T10:04:31.215Z`; a value may carry a UTC offset. Latitude and Longitude cannot be used in a rule. A value the field cannot take stops the step with a message naming the field. A blank value on **Contains**, **Starts with** or **Ends with** stops the step too, since it would match every record.
- **Enriched Company fields** (Employee range, Estimated ARR, Funding raised) are read-only and cannot be used in a rule: Attio fills them by enrichment.
- **Dates** are compared by calendar day.
- A rule that matches nothing returns no records; the workflow continues with empty variables.

### Reading Record Data

| Attribute type | Reads as |
| --- | --- |
| Select, Status | The option or status title, for example `Won 🎉` |
| Currency | The amount only, for example `48000` |
| Several values (Email addresses, Phone numbers, Domains, multi-select, several linked records) | One text, values separated by `; `: `jane.doe@example.com; jane@example.com` |
| Phone numbers | International format, for example `+14155550132` |
| Linked records (such as **Company** on a person, **Associated deals**) | The **Record ID** of the linked record, not its name |
| Workspace members (such as **Deal owner**, **Created by**) | The member's ID; on a write, the login email of an active member also links them |
| Date | Midnight UTC on that day: `2026-12-15T00:00:00.000Z` |
| Date and time | UTC: `2026-09-22T23:40:10.000Z` |
| Checkbox | `true` or `false` |

- Only the current value of each attribute is read, not its history.
- Empty fields are left out of the result.
- To read a linked record's own fields, such as the name of a person's company, add a second Read step on that object and match its **Record ID** to the linked Record ID.

### Writeback Behaviors

| Topic | Behavior |
| --- | --- |
| Mapped fields | Written. Fields you do not map are left as they are. |
| Several values | Separate them with `;`: `jane.doe@example.com; jane@example.com` writes two email addresses. On **Update**, the values you send replace the ones the record has. |
| Blank values | An empty value clears the field, on every type. A required field (such as **Deal name**, **Deal stage**, **Deal owner**) cannot be cleared on an update: the step stops naming the field. |
| Numbers | A number, currency or rating takes a number or a numeric text with a dot as the decimal separator (`12000`, `12,000.50`); `12,5` stops the step naming the field. |
| Titles | A select or status title is matched exactly, after leading and trailing spaces are removed. |
| Ratings and checkboxes | A rating is a whole number from 0 to 5. A checkbox takes **true** or **false** (any case); other words stop the step naming the field. |
| Email addresses and phone numbers | Each address in a `; ` list must be an email address and each phone number must start with `+` and the country code (`+14155550199`); a value that is not stops the step naming it, and nothing in the list is written. |
| Text | A number or true/false mapped into a text field is written as text. Spaces around a value are removed; a value that is only spaces clears the field. |
| Names | **Full name**, **First name** and **Last name** cannot be mapped to a blank value; a Create step whose every mapped field is blank stops instead of creating an empty record. |
| One value per field | Map one field of a Read step's output to a field, never the whole output; a field that receives an object stops the step naming the field. |
| Unique values | An email address or a company domain that another record already has stops the step naming the value; find that record with a Read step on the field. Two Create steps that race for the same address never both succeed. |
| Locations | Mapping one part of a location (such as **City**) keeps the other parts; blanks on every part clear the location. **Latitude** and **Longitude** are decimal numbers with a dot, **Postcode** is text (a number is written as text), and **Country code** is a two-letter code such as `CA` (lower case is accepted). A value outside those forms stops the step naming the part. |
| Company domains | **Domains** takes a host (`acme.com`, `www.acme.com`) or a URL; Attio keeps the bare host. A domain on a reserved top-level domain stops the step naming the values sent. |
| Date-times | Map a date-time with its zone. A calendar day written to a date-time field lands at that day's midnight UTC, and a value without a zone is read as UTC. |
| Select, Status | Written by the option or status title, exactly as it appears in Attio. The value must already exist: the app does not create options. |
| Name | Map **Name: First name** and **Name: Last name**, or **Name: Full name**. On **Update**, a part you do not map keeps its current value. |
| Location | On **Update**, a part you do not map keeps its current value. |
| Linked records | Map the **Record ID** of the record to link, for example the Record ID from a Read step on Companies. A company can also be linked by its **domain** (`acme.com`) and a person by an **email address**. The exact **name** of a record links it when exactly one record of that object has that name; a name no record has, or one shared by several records, stops the step. A domain is the bare host (`acme.com` or `www.acme.com`, not a URL); email addresses match regardless of case. Several values that resolve to the same record (two addresses of one person) link it once. A Record ID of another object stops the step. |
| Dates | Written as the calendar day (`YYYY-MM-DD`) the value starts with. |
| Phone numbers | Attio checks that the number is real. Use international format: `+14155550132`. |
| Currency | The amount only; the currency comes from the attribute's settings in Attio. |
| Required attributes | Attributes your workspace marks as required must be mapped on **Create**. The standard People object requires none. |

Attio checks every value. When Attio refuses one, for example an option that does not exist or a phone number that is not real, the step stops with a message that names the field; for a select or status value it lists the accepted titles, which are matched exactly, including case and emoji.


## 3. Installation and Configuration

### Prerequisites

- An **Attio** workspace, and an Attio user with access to the records your workflows will use.
- A **Docusign** account with admin rights to install and manage apps in the App Center.

### How to Install the App

- Open the [**Docusign App Center**](https://apps.docusign.com/app-center/extensionapps) and search for **Attio** in the search bar.

  ![Docusign App Center search results showing the Attio extension app by Fluidlabs.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/app-center-search.webp)

- Click the **Attio** app card to open its detail page, then click **Install App**.

  ![The Attio app page in the Docusign App Center with the Install App button.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/app-install.webp)

- Review the access the app requests and click **Install and Authorize**.

  ![The Install and authorize Attio app screen listing the requested access, with the Install and Authorize button.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/install-authorize.webp)

The app now appears with an **Installed** status.

### Connecting Your Account

- On the installed app page, click **Connect Account**.

  ![The installed Attio app page showing the Connect Account button.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/connect-account.webp)

- **Connection Visibility**: choose how the connection is shared:

  - **Private**: accessible only by you in Docusign.
  - **Shared**: accessible by multiple users or the whole team.

  ![The Connection Visibility step with Private and Shared options.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/connection-visibility.webp)

- **Name Connection**: enter a name. It appears in workflow steps, so make it easy to identify. Click **Log In**.

  ![The Name Connection step with a connection name entered.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/name-connection.webp)

- Sign in to Attio if you are not signed in already.

- On the Attio access request, the app is named **Docusign IAM Workflows**. Review the workspace scopes it requests and click **Confirm**.

  ![The Attio access request for Docusign IAM Workflows listing the requested workspace scopes, with Cancel and Confirm buttons.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/attio-consent.webp)

- If you click **Cancel** instead, Attio takes you to your workspace home in the same window; the window does not close. This is Attio's standard behavior and no connection is created. Close the window and start again from **Connect Account** when you are ready to connect.

The connection is added and ready to use in workflow steps. Each connection works with one Attio workspace: the one the access request was confirmed for.

### Managing Connections

On the Attio app page, open the **Manage** dropdown.

![The Manage dropdown on the Attio app page showing New Connection, Manage Connections, Manage Apps, and Uninstall App.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/manage-connections-menu.webp)

Select **Manage Connections** to see every connection.

![The Attio connections list showing a connection with an Active status and the New Connection button.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/connections-list.webp)

Use the three-dot (⋮) menu next to a connection:

![The connections list with the three-dot menu open showing Edit connection name, Reconnect, Reload Objects, and Delete Connection.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/connections-actions-menu.webp)

- **Edit connection name**: rename the connection.
- **Reconnect**: sign in to Attio again. Use it when a step reports that the connection must be reconnected.
- **Reload Objects**: refresh the objects and fields. Run it after you add, rename or change objects or attributes in Attio.
- **Delete Connection**: remove the connection. ⚠️ This may break workflows that use it.

### Adding a New Connection

Use **Manage → New Connection** on the app page, or **+ New Connection** on the Connections page. Each connection appears separately in workflow steps. To work with a second Attio workspace, add a connection while signed in to that workspace in Attio.

### Revoking Access from Attio

In Attio, open **Workspace settings → Apps → Docusign IAM Workflows**. The **Connections** tab lists the access granted to the app, and **Uninstall** removes the app from the workspace. Every Docusign connection to that workspace then stops working until it is reconnected.


## 4. How to Use the App

### Create a Workflow

- Log in to Docusign and go to **Agreements → Workflows**.
- Click **Create Workflow**.

  ![The Docusign Workflows screen with the Create Workflow button.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/workflow.webp)

- Build your workflow using the available steps, including the Attio actions.
- Publish the workflow when it is ready.

### Available Attio Actions

Click **+ Add Step** and search for **Attio**:

![The Add New Step dialog with "Attio" searched, showing Writeback to Attio and Read from Attio.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/add-step-actions.webp)

- **Read from Attio**: fetch a record of any object and expose its fields as workflow variables. See [Read from Attio](https://fluidlabs.com/documentation/attio-for-docusign-iam#5-read-from-attio).
- **Writeback to Attio**: create or update a record. See [Writeback to Attio](https://fluidlabs.com/documentation/attio-for-docusign-iam#6-writeback-to-attio).
- **File Upload**: store a document from the workflow in a record's **Files**. The step is named **File Upload** and carries the Attio logo, so search for **File Upload** to find it. See [File Upload to Attio](https://fluidlabs.com/documentation/attio-for-docusign-iam#7-file-upload-to-attio).

A typical sales flow:

1. **Read from Attio**: find the person, and the deal or company for the agreement details.
2. **Prepare eSignature Template**: pre-fill the order form or contract.
3. **Send Documents for Signature**.
4. **File Upload**: file the signed agreement on the person or deal.
5. **Writeback to Attio**: move the deal to a new stage or update the record.


## 5. Read from Attio

The **Read from Attio** step retrieves a record and exposes its fields as workflow variables.

### Start the Workflow

The example below starts the workflow **From an API Call** with one **Text** variable, `record_email`, that carries the person's email address. Any start type works: with a web form, use the form's email field wherever this example uses `record_email`.

![The Add workflow start panel: From an API Call with a Text variable named record_email.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/read-workflow-start.webp)

### 1. Add the Read Step

On the workflow canvas, click **+ Add a step** below the start.

![The workflow canvas with the Add a step button below Start Workflow.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/read-add-step-canvas.webp)

Search for **Attio** and select **Read from Attio**.

![The Add New Step dialog with Read from Attio highlighted.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/read-add-step-search.webp)

### 2. Configure Connection and Object

- **Connection**: select the connection you created during [installation](https://fluidlabs.com/documentation/attio-for-docusign-iam#3-installation-and-configuration).

  ![The Read step Connection dropdown showing the Attio connection.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/read-configure-connection.webp)

- **Attio object**: choose the object to read. The list holds every object of your workspace. This example uses **People**.

  ![The Attio object dropdown showing Deals, Companies and People.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/read-configure-object.webp)

Click **Next**.

### 3. Select Fields

Click **Add or Remove Fields** and tick the fields your workflow needs. The selected fields become workflow variables for later steps.

![The field browser listing People fields with checkboxes, among them Record ID, Company, Description and Email addresses.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/read-fields-browser.webp)

The list shows every attribute of the object in your workspace, custom attributes included, plus **Record ID**. How each type reads is under [Reading Record Data](https://fluidlabs.com/documentation/attio-for-docusign-iam#2-implementation-guide--known-behaviors).

Click **Next**.

### 4. Identify the Record

Create a rule that tells the step which record to read. In this example, match the person's **Email addresses** to the `record_email` start variable:

- **Attio field:** Email addresses
- **Operator:** Equal to
- **Workflow field:** `record_email`

![The record-matching rule: Email addresses equals the record_email variable, with A single record selected.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/read-identify-record.webp)

Under **How many records should this step return?**, pick one:

- **A single record**: the first record that matches.
- **Multiple records**: up to five.

Use **preview this step** to check the rule against live data, then click **Apply**.

![The preview of a Read step showing one person's fields as read from Attio; Company shows the Record ID of the linked company.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/read-preview.webp)

Which fields and operators a rule can use is under [Searching for a Record](https://fluidlabs.com/documentation/attio-for-docusign-iam#2-implementation-guide--known-behaviors).


## 6. Writeback to Attio

The **Writeback to Attio** step creates a record or updates one.

### 1. Add the Writeback Step

On the workflow canvas, click **+ Add a step** where the writeback belongs, then search for **Attio** and select **Writeback to Attio**.

![The Add New Step dialog with Writeback to Attio highlighted.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/writeback-add-step-search.webp)

### 2. Configure Connection, Object, and Write Setting

- **Connection**: select your Attio connection.

- **Attio object**: choose the object to write. This walkthrough uses **People**.

  ![The Attio object dropdown for the Writeback step.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/writeback-configure-object.webp)

- **Write settings**:

  - **Update or Create**: updates the matching record, or creates one if the rule finds nothing.
  - **Update**: updates an existing record only.
  - **Create**: always creates a record.

  ![The Write settings options: Update or Create, Update, and Create.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/writeback-write-settings.webp)

Click **Next**.

### 3. Map Fields

Click **Add or Remove Fields** and tick the fields you want to write. Only attributes Attio lets you edit are listed: Record ID and fields such as **Created at** do not appear.

![The field browser listing the writable People fields with checkboxes.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/writeback-fields-browser.webp)

Each selected field gets its own row. Map it to the workflow variable that supplies the value, or type a value.

![The Writeback step with Description mapped to a typed value.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/writeback-map-fields.webp)

In this example the step updates the person the Read step found and sets **Description** to `Order form sent for signature`.

⚠️ **Map from the right source.** The variable picker also lists the output of your **Read from Attio** step. Mapping from there writes the original values back unchanged. Map new values from the step that collected them, such as a start variable or a web form, or type them.

Click **Next**.

### 4. Identify the Record

Match the record by **Record ID**, or by an attribute such as **Email addresses**:

- **Attio field:** Record ID
- **Operator:** Equal to
- **Workflow field:** the **Record ID** of the Read from Attio step (**Person / Record ID**)

![The record-matching rule for Writeback: Record ID equals Person / Record ID from the Read step.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/writeback-identify-record.webp)

Click **Apply**.

With **Update or Create**, a rule that finds no record creates one; running the workflow again with the same value updates it.


## 7. File Upload to Attio

The Attio **File Upload** step files a document produced earlier in the workflow in a record's **Files** in Attio. Maximum size is 50 MB.

### 1. Add the File Upload Step

Add a step after signing completes, search for **File Upload**, and select the **File Upload** step with the Attio logo. Searching for "Attio" does not list it.

![The Add New Step dialog with "File Upload" searched and the Attio File Upload step highlighted.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/file-upload-add-step-search.webp)

### 2. Select the File

Choose the file or envelope from an earlier step, for example the **Combined Envelope File** from **Send Documents for Signature**.

![The file picker showing the envelope files of the signing step.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/file-upload-select-file.webp)

> An empty list means no earlier step in the workflow produced a file.

### 3. Choose the Object

- **Select connection**: your Attio connection.
- **Select drive**: each drive is one of your Attio objects, such as **People (use Record ID as subfolder)**. Pick the object of the record that should hold the file.

  ![The Select drive dropdown listing Deals, Companies and People, each marked use Record ID as subfolder.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/file-upload-select-drive.webp)

### 4. Point the Folder at the Record

The folder tells the app which record gets the file. Attio creates no folder.

**Use the Record ID from an earlier step** (recommended, it works for every record the workflow handles):

- Click **Add Folder**, open the **Select folder** dropdown and pick **New Subfolder**, the last entry of the list. The **New folder** dialog opens.

  ![The New folder dialog with the Add Variable and Add Text buttons.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/file-upload-new-subfolder.webp)

- Click **Add Variable**, choose the step that returns the record, select **Record ID** (**Person / Record ID** for a Read step on People) and click **Add**.

  ![The variable picker listing the fields of the Read from Attio step, with Person / Record ID highlighted.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/file-upload-add-variable-record-id.webp)

- **Select folder** now shows the Record ID variable. Click **Next**.

  ![The File Upload location with the connection, the People drive, and Person / Record ID as the folder.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/file-upload-location-set.webp)

**Or pick one record from the list.** The **Select folder** dropdown lists the object's records by name followed by `#` and the Record ID, for example `Jane Doe#45c73e56-362d-4108-b8c2-460b632c4689`. A picked record receives the file on every run, so use this only for a workflow that always files to the same record.

![The File Upload location with Jane Doe#45c73e56-362d-4108-b8c2-460b632c4689 picked in Select folder.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/file-upload-select-folder.webp)

The list shows up to 500 records, and a record without a name is listed by its Record ID. Use the Record ID variable for objects with more records.

### 5. Name the File

Build the file name from **Add Text** and **Add Variable**. A date or time variable keeps repeat runs apart.

![The file name step with a text chip, the Person / Name: Full name variable and a .pdf text chip.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/file-upload-file-name.webp)

In a variable's value, characters other than letters, digits, `.` and `-` are replaced with `_`: the name `Jane Doe` becomes `Jane_Doe`, and a time `10:00:00` becomes `10_00_00`. Text you type is kept as it is. The file keeps the document's extension: `.pdf` is added when the name does not end with it, and never twice. The example above produces `Signed MSA - Jane_Doe.pdf`.

Click **Apply**.

### 6. Verification

After the workflow runs, the document appears in the record's **Files** in Attio.

![The Files tab of the person in Attio listing Signed MSA - Jane_Doe.pdf.](https://fluidlabs.com/images/documentation/attio-for-docusign-iam/file-upload-verification.webp)


## 8. FAQ & Troubleshooting

**A step failed.**
> The usual causes: a value for a select or status attribute that does not exist in Attio, a phone number Attio does not accept, a Record ID that belongs to another object, a linked record named by a name that no record has or that several records share, a required attribute left unmapped on Create, or an Attio connection that was removed from the workspace.

**Can I link a record by name instead of its Record ID?**
> Yes, when the name belongs to exactly one record of that object. Companies can also be linked by domain and people by email address. For a workflow that handles many records, map the **Record ID** from a Read step: names can be shared or renamed.

**My step uses the User or Workspace object, or a field such as Associated users.**
> Those objects and their link fields are no longer available in the app. Run **Reload Objects** on the connection, then delete the step and build it on People, Companies, Deals or a custom object.

**A field I expect is missing from the step.**
> Open **Manage Connections**, click **Reload Objects** on the connection, then reopen the step and select the field again.

**A step that worked before now fails after I changed an attribute in Attio.**
> Run **Reload Objects**. If you changed the attribute's type, delete the step and add it again: a step keeps the fields it was built with.

**I clicked Cancel on the Attio access request and the window now shows my Attio workspace.**
> That is Attio's standard behavior when access is declined: it returns you to your workspace home in the same window instead of closing it. No connection was created. Close the window and click **Connect Account** again when you want to connect.

**The step says the connection must be reconnected.**
> Attio no longer accepts the connection, usually because the app was removed from the workspace. Click **Reconnect** under **Manage Connections**.

**A step reports a missing permission.**
> The Attio app lacks access to that kind of data. Contact Fluidlabs support.

**Company or Deal owner reads as a long ID instead of a name.**
> Linked records and workspace members are read as IDs. Add a Read step on the linked object with its **Record ID** to get its fields.

**My update replaced all the email addresses.**
> On **Update**, the values you send for an attribute with several values replace the existing ones. Send every value, separated by `;`.

**A select or status value is refused.**
> The value must match an existing option or status title in Attio. The app does not create options.

**Why can't I combine Record ID with other conditions?**
> Record ID fetches exactly one record. Use it alone, or build the rule from other fields.

**I only see "Equal to" in the Operator list.**
> Equal to is the operator the step offers. To narrow a search further, add conditions with AND.

**I searched for "Attio" and the File Upload step is missing.**
> The step is named **File Upload**. Search for "File Upload" and pick the one with the Attio logo.

**The folder list shows long IDs instead of names.**
> A record without a name is listed by its Record ID. Use the Record ID variable from a Read step instead of picking from the list.

**The file picker says no files are available.**
> No earlier step produced a file. Add the upload after **Send Documents for Signature**.

**The file did not appear on the record.**
> The folder has to hold the record's Record ID, from a step that runs before the upload, and the drive has to be that record's object.

---

Attio for Docusign IAM is published by Fluidlabs. Docusign is a trademark of Docusign, Inc.
