> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/connectors/custom-connector/custom-connector-scripting-reference/email-challenge-template-selection.md).

# Email challenge template selection

Override which email template is used for an email-based account challenge, using \`runtime.emailAccountChallenger.templateFinder\`.

This optional hook overrides which email template The Wallet Crew uses when it sends an email-based account challenge — the confirmation email sent during pre-registration or account verification flows that use the email challenger. It needs no additional configuration — registering the endpoint in a script is enough for it to be called.

```js
/**
 * @param {Record<string, any>} data - Contextual data available to the challenge (entity values, the generated authentication token, etc.).
 * @param {string} defaultTemplateName - The template name configured for the email challenger.
 * @returns {Promise<string|null>} The template name to use, or null to send no email at all.
 */
async function getEmailTemplate(data, defaultTemplateName) {
  if (data["storeId"] === "vip-store") {
    return "vip-account-challenge";
  }
  return defaultTemplateName;
}

export default function (context) {
  context.register('runtime.emailAccountChallenger.templateFinder', {
    GetEmailTemplate: getEmailTemplate
  });
}
```

{% hint style="info" %}
Returning `null` cancels the email entirely for that challenge — no email is sent. This is distinct from returning the default template name unchanged.
{% endhint %}

If this endpoint is not registered, the email challenger falls back to the template name from its own configuration.


---

# 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://docs.thewalletcrew.io/connectors/custom-connector/custom-connector-scripting-reference/email-challenge-template-selection.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.