> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/workflows/actions-catalog/sendgrid.md).

# Sendgrid

## Why using the Sendgrid action?

With the Sendgrid action anybody in your organisation can send data directly via email. 

This is useful to quickly share with teammates any updates on current deadlines on vital informations based on data.

{% hint style="info" %}
The Sendgrid integration allows you to own the email provider used to send emails. If you don't want to use sendgrid, you can also used the Whaly Email service that is configured by default on your workspace.
{% endhint %}

## What does it look like?

This action will send a screenshot of your dashboard/question as an email attachment to who ever you want while using your Sendgrid account.

## Supported formats

Slack integration supports the following formats:

* PDF
* PNG

## Configuring Sendgrid

In order to configure the Sendgrid action, you need to get a Sendgrid API key. 

In order to get a sendgrid API Token, please follow [this documentation](https://docs.sendgrid.com/ui/account-and-settings/api-keys). Whaly needs an api key with permission to send emails.


---

# 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.whaly.io/workflows/actions-catalog/sendgrid.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.