> For the complete documentation index, see [llms.txt](https://docs.feedotter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feedotter.com/automations/getting-started/sfmc-sending.md).

# SFMC Sending

{% hint style="info" %}
If you haven't integrated your ESP in the settings yet, it's best to do that before finalizing your automated campaign. [Click here to learn how.](/integrations/salesforce-marketing-cloud.md)
{% endhint %}

### Finalize Your SFMC Automation Settings <a href="#headline-60-20978" id="headline-60-20978"></a>

When you are within your automated campaign, select the **Integration** tab on the left sidebar. &#x20;

Click Connect, then you will see this:

<div align="left"><figure><img src="/files/enlFWqKu6Rf8uAVBSf2G" alt="" width="375"><figcaption></figcaption></figure></div>

We have found most customers already have these items in place but a couple items you will want to have handy are:

* **Data Extension:** FeedOtter will automate the sending of blog newsletters to recipients based on a data extension that you create. This data-extension MUST have a field named "email."  This is fairly standard in Salesforce Marketing Cloud.
* **Send Classification:** Send classification settings will override FROM and REPLY-TO settings in the FeedOtter Application.

Ensure to fill in all required fields, then click **Activate Campaign.**&#x20;

After activation, you can monitor and manage your automation from either the **Automations** dashboard or the **Automation Details** page.&#x20;

{% content-ref url="/pages/qpMKtJKyYL08DaTQAjQV" %}
[Automation Details](/automations/automation-details.md)
{% endcontent-ref %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.feedotter.com/automations/getting-started/sfmc-sending.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
