Gmail’s current documentation calls canned responses Templates. On a computer, enable Templates in Gmail settings, save a composed message, and insert it from the compose window whenever you need it. A support agent, for example, can save a business-hours reply with plain-text markers such as [Name] and [Hours], then complete and review those fields before sending.
This guide covers the documented Gmail web workflow for creating, inserting, updating, and deleting templates. It also separates two different automation choices: a Gmail filter that sends a saved template for narrowly defined criteria, and an application that creates Gmail API drafts for review. Setup time depends on your account, interface, and message complexity.
How Gmail templates work
A Gmail template is reusable message content saved in Gmail. A person selects it while composing an email. Text such as “Hi [Name]” is ordinary text that someone must replace; Gmail’s documented template workflow does not provide dynamic fields or automatic personalization.
Use built-in Gmail Templates when your team mainly works in Gmail and needs a small library of repeated messages. Google documents this workflow for Gmail on a computer. The current instructions do not establish the same workflow in the Gmail mobile app, so use the web interface for the steps below. Labels can vary slightly by account rollout or localization.
Enable Templates and create your first reusable message
- In Gmail on a computer, select Settings, then See all settings.
- Open the Advanced tab. Under Templates, select Enable, then select Save Changes.
- Select Compose and write the reusable message. Give it a clear name, such as “Appointment confirmation,” and mark information that must change for each recipient with obvious text such as [Name], [Date], or [Next step].
- In the compose window, select More options, the three-dot menu, then Templates > Save draft as template > Save as new template. Enter a name and save it.
- Open a new compose window and check More options > Templates to confirm that the item appears.
The composed message becomes the reusable content. The bracketed fields remain text for a person to complete. See Google’s Gmail template instructions for the current interface.
Insert, edit, and delete a Gmail template
Insert a template
- Select Compose.
- In the compose window, select More options > Templates > Insert template, then choose the saved template.
- Complete the message and review the recipient, subject, links, names, dates, and placeholders before sending. Google’s current instructions do not promise that the template name populates the subject line.
Update an existing template
Compose or insert the revised message. Select More options > Templates > Save draft as template > Overwrite Template. Select the target template and save. This updates the existing named copy rather than creating another template.
Delete a template
Select More options > Templates > Delete template, choose the item, and confirm. Check the name before confirming because Google warns that deleted templates cannot be recovered.
Manual insertion or automatic sending with a Gmail filter?
Manual insertion adds saved content while a person is composing. A Gmail filter can instead apply search criteria and use the Send template action to send a selected template automatically. The filter evaluates its defined criteria; it does not interpret the meaning or intent of a message.
Hypothetical workflow: A support team wants to send a business-hours response to mail addressed to [email protected] when the subject contains a known “hours” token. Before activation, the team tests those criteria against representative messages. Messages involving refunds, cancellations, legal matters, or security are excluded from the automatic path and assigned to a named reviewer. The criteria, exclusions, and review assignment are proposed operating controls, not features supplied automatically by the Send template action.
To configure the documented Gmail action, save the template first, create a filter with the intended search criteria, select Send template, choose the saved message, and create the filter. Test the search criteria before activation and keep them narrow and stable.
Use a Gmail filter when the trigger is explicit, such as a known sender, routing address, label, or subject token. If the right response depends on interpreting ambiguous meaning, route the message to a person instead of broadening the auto-send rule. A bounded classifier may be considered for semantic cases, but uncertain or sensitive results should stop at human review. AI agent services may be relevant to that reviewed workflow, not to enabling Gmail Templates.
Can Gmail templates be managed through the Gmail API?
Google’s public Gmail API reference documents drafts and messages but does not list a dedicated Gmail message-template resource or template create, list, update, and delete methods. An API-created draft is therefore not the same object as a saved Gmail UI template. Use Gmail’s web interface for built-in template management.
For an application-driven workflow, keep reusable content and its versions in the application, then use documented Gmail API draft operations. A draft is useful when a person must approve a response before it is sent. The API supports creating, updating, listing, retrieving, deleting, and sending drafts. Sending a draft deletes the draft and creates a sent message with a new message ID. Drafts contain MIME messages, and each operation requires compatible OAuth scopes. Review Google’s draft guide, Draft resource reference, sending guide, and quota guidance before implementation.
A proposed draft-first sequence is: identify the source message, apply deterministic exclusions, select an approved application-managed template version, construct a MIME message, create a Gmail draft, obtain approval when required, send it, and record the outcome. This is an integration pattern, not a ready-made connector. If a broader workflow is needed, Zapier automation consulting can help evaluate connector, authorization, and action requirements before anyone promises a live integration.
Use the right record grain
One processing record should represent one source Gmail message event for one workflow version. A generated draft, an approval decision, and an actual send are different records or event types. A thread ID alone is not a safe duplicate key because one thread can contain multiple messages.
The following is an illustrative application record for one processing event, not a Gmail-native template object. Its proposed uniqueness key identifies the processing row by account, source message, workflow version, and action type:
{
"account_id": "acct_123",
"source_message_id": "msg_456",
"workflow_version": "support_reply_v1",
"action_type": "create_draft",
"template_key": "business_hours",
"template_version": "3",
"draft_id": "draft_id_from_api",
"approval_status": "pending",
"send_status": "not_sent"
}Enforce uniqueness with a database constraint or atomic upsert. A lookup followed by create is not sufficient when concurrent workers can process the same message. Track approval decisions and send attempts at their own grain, and store the resulting sent-message ID after a successful send. If an API call times out, reconcile the provider state before retrying so an uncertain result does not create a duplicate draft or send.
Before creating or sending a draft, validate the sender account, recipient, required fields, unresolved placeholders, policy exclusions, approved template version, authorization scope, and duplicate-processing state. Use quota-aware retries with backoff, and send uncertain or sensitive cases to a named human reviewer.
- Manual Gmail: confirm the sending account, recipient, subject, links, dates, completed placeholders, and sensitive information.
- Automatic filter: test representative matches, inspect exclusions, and assign a human owner for misrouted or high-impact messages.
- API workflow: record the source message ID, account identity, template key and version, draft ID, approval status, send status, and resulting sent-message ID in the application.
- API workflow: enforce a uniqueness constraint or transactional upsert for the declared processing grain, and verify OAuth scopes and current quotas.
A practical pre-send and launch check
For a manual reply, the composing Gmail user owns the final review. For an automated workflow, the application should record its processing state before external actions, validate the selected version, and provide an owner for exceptions. Keep the manual, filter, and API paths distinct so users know which system controls the message.
Measure actual template reuse, how often users correct inserted content, and review time. These measures show whether templates help in your context without assuming a guaranteed time saving or business outcome. For API drafts, reconcile timeouts against recorded draft and sent-message state before retrying.