Green Doors is a free property management platform. Manage your properties with an easy-to-use and powerful platform.

Green Doors

Select your Team or leave empty to use your Personal account.

Should this trigger fire when a SignRequest is fully Signed or Declined or you've Received a new SignRequest?

Optionally use a Team account when sending the SignRequest or leave empty to use your Personal account.

**You have 2 options to create a SignRequest:**

1. *Upload a File*: Use a trigger that provides a File Object.
2. *Provide an URL*: SignRequest will download the document from that location.

*Option 1: Upload a File*

PDF's are preferred. If you do not provide a File here you need to provide a url in 'File From Url' where SignRequest can download the file.
Generally you'll want to use this if your trigger provides a File Object.

*Option 2: Provide an URL*

When not using 'File' provide a url here where SignRequest can download the file.
If the download location returns a content type of *text/plain* or *text/html* SignRequest will do its best to *make a pdf* out of it. This can be used if you want to dynamically create pdf documents from web pages without making a pdf yourself.

By default the Sender is the email address of the connected SignRequest account.
When using a Team this may also be one of email addresses of Team members.

By default only the signer(s) you add need to sign. If the Sender also needs to sign, choose 'Me & Others'.

By default we use the filename as the name of a SignRequest.

Generally you'll want to leave this empty as SignRequest generates one automatically.

A custom message to show in the SignRequest email. If left empty SignRequest will generate one for you.

Automatically remind signer(s) when the document hasn't been signed.

The email address of the signer. When multiple emails are added these signers will all have the same configuration and receive a SignRequest. When different configurations are required for separate signers please use the 'Advanced Signers Configuration' field.

Set to 'no' if this signer only needs to receive a copy of the signed document.

Set to 'yes' if this Signer only needs to approve this document ('approve' button instead of signature).

By default all signers receive the SignRequest at the same time. If you want a signer to receive the SignRequest after another signer has signed increase the order level for that signer. E.g. if you have one signer with order 0 and two with order 1, the two with order 1 will get the SignRequest simultaneously when the signer with order 0 has signed (or approved). Generally useful when a document must first be approved internally before it goes to a customer.

Sets the language of the SignRequest emails. While signing the browser of the signer determines the language of the interface.

To force the SignRequest browser interface to use the Signer Language set this to 'yes'. By default the browser language settings are used.

To enable Text Message Verification provide a mobile phone number **including the country code**.

For advanced users only. This field can be used to used when multiple signers or complex setups are required. This overrides all other signers related configuration fields. The value must be a valid JSON structure (array). Please note that there should be no `,` after the last Object `{...}` in the list.

For example to have the first signer to only approve a document and send the second SignRequest to the second signer only after the first signer has approved:

```
[
{"email": "first_signer@example.com", "needs_to_sign": true, "approve_only": true, "order": 0},
{"email": "second_signer@example.com", "needs_to_sign": true, "order": 1}
]
```

To just have 2 signers: sign a document at the same time:

```
[
{"email": "first_signer@example.com"},
{"email": "second_signer@example.com"}
]
```

Please also refer to our API documentation for all possible configuration options for the signer object: [https://signrequest.com/api/v1/docs/](https://signrequest.com/api/v1/docs/). You can also l...

For advanced users only. This field can be used to prefill (template) tags in a document. The value must be a valid JSON list structure (array). Please note that there should be no `,` after the last Object `{...}` in the list.

Example:

```
[
{"external_id": "customer_name", "text": "John Smith"},
{"external_id": "customer_birth_date", "date_value": "1984-12-31"},
{"external_id": "customer_city", "text": "New York"},
{"external_id": "checkbox_1", "checkbox_value": "true"},
{"external_id": "checkbox_2", "checkbox_value": "false"}
]
```

The "external_id" is the External ID set when creating a template tag. The "date_value" field must be in ISO format ([YYYY]-[MM]-[DD]). The "checkbox_value" can only be "true" or "false". The "text" field may have any value.

Please also refer to the [api documentation](https://signrequest.com/api/v1/docs/) and our [help section](https://help.signrequest.com/hc/en-us/articles/115002895645-How-to-create-templates-) on the topic.

*Please note that wh...

Optionally use a Team account when sending the SignRequest or leave empty to use your Personal account.

The templates you can select depend on whether or not you've selected a Team.

*Note: If you get the error 'Invalid hyperlink - Object does not exist.' this means that you've changed your Team / Personal account after selecting a template. Please make sure the selected template is available for your current Team.*.

To learn more, read the [SignRequest API Documentation](https://signrequest.com/api/v1/docs/)

Select “Yes” to [stop this Zap step](https://help.zapier.com/hc/en-us/articles/20505304170637-Review-Zap-run-statuses#h_01HD20969HPZ01ENM30NQR79X5) if the app returns an error and enable automatic authentication refresh. Select “No” to run the Zap step regardless of errors. Learn more about [API Request action error handling](https://help.zapier.com/hc/en-us/articles/12899473501453#h_01JKRBY68EDXBB1V817DSTRZ0N).

Requests can only be made to domains associated by this application. Read more about [API Request Setup](https://help.zapier.com/hc/en-us/articles/12899607716493).

Any parameters added to a URL will be URL-encoded and appended to the request URL to pass additional data to the API request.

These headers and values will be applied to the request in addition to any headers created as part of authentication. Authentication headers are added automatically.

Zapier will pass this along raw. If you would like to provide complex JSON, try a "Code by Zapier" step to build the structure and pass it along here. For example, `{"foo": "bar"}` is perfectly valid.

SignRequest is an electronic (digital) signature solution to get documents signed. Easy, fast, secure and legally binding.

SignRequest

Send your lease documents out via SignRequest when you publish the lease on Green Doors.

Green Doors + SignRequest

Send SignRequests from templates in SignRequest for new Green Doors publish leases

Supported triggers and actions

Publish Lease

New Document Received

Send SignRequest

API Request (Beta)

New Document Declined

New Document Signed

Send SignRequest From Template

About Green Doors

Related categories

About SignRequest

Related categories