> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/templates/send-from-a-template.md).

# Send from a template

Start a new request from a saved template, add recipients and send.

Sending from a template fills in a new request with everything the template holds. You add the recipients, adjust anything for this client, and send.

{% stepper %}
{% step %}

### Pick the template

Click the arrow next to **New Request** in the left sidebar. The **Create from Template** menu lists your own templates and the ones teammates have shared with you. Type in **Search** to filter by name, then click a template.

If the menu says **You don't have any templates**, click **Create One**. See [Create and edit templates](/templates/create-and-edit-templates.md).
{% endstep %}

{% step %}

### Add recipients and adjust

The new request opens with the template's checklist, attachments, forms, recipient roles, tags and reminder frequency already filled in. The expiration date is set to today plus the template's **Days To Expire**.

Add each recipient's name and email address (or phone number, on plans with [SMS reminders](/reminders-and-notifications/sms-reminders.md)). If the template has more than one recipient role, the page adds a recipient card for each role.

Change anything you need. Edits apply only to this request; the template stays as it was.
{% endstep %}

{% step %}

### Send

Click **Next**. The **Send Request** dialog is prefilled with the template's subject, message, export folder, language and notification sequence (under **Advanced**). Click **Send Request**.
{% endstep %}
{% endstepper %}

## What carries over, and what doesn't

| From the template                                        | On the new request                                                             |
| -------------------------------------------------------- | ------------------------------------------------------------------------------ |
| Checklist, sections, instructions, attachments and forms | Copied. Changing the template later doesn't change this request.               |
| Tags, reminder frequency, subject, message, language     | Copied, and editable before you send.                                          |
| Days To Expire                                           | Turned into an expiration date counted from today.                             |
| Notification sequence                                    | Linked, not copied. Edits to the sequence apply to every request that uses it. |
| Cloud export folder                                      | Applied only if you have access to that integration.                           |
| Recipients                                               | Never stored in a template. You add them each time.                            |

## Other ways to send from a template

* **Bulk send** sends one template to many recipients at once, each getting their own request. See [Bulk send](/requests/bulk-send.md).
* **Lead forms** create a request from a template whenever someone fills in your public form. See [Lead forms](/intake/lead-forms.md).
* **The API** can create a request from a template. See the API Reference section.

<details>

<summary>I can't find a teammate's template in the menu</summary>

A teammate's template appears only after they share it with the team. If it's shared with specific user groups, only members of those groups see it. When the **Shared inbox** setting in [Team → General](https://pipefile.com/dashboard/settings/team#general) is off, you see only templates shared by team admins. See [Share, lock, reorder and duplicate templates](/templates/share-lock-reorder-and-duplicate.md).

</details>

<details>

<summary>Can I send from a locked template?</summary>

Yes. Locking stops teammates from editing or deleting the template, not from sending it. You can still change the new request before sending.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.pipefile.com/templates/send-from-a-template.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.