> For the complete documentation index, see [llms.txt](https://help.marketguard.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.marketguard.io/marketguard/integration-guide.md).

# Integration guide

Get ready with third-party integrations.  

1. **Slack**. To get notifications to Slack, you need to create a webhook.
2. **SumSub**. 

    \- Create a questionnaire that your clients will use during onboarding 

    \- Create an API key

    \- Create a webhook
3. **Email**. Create a new email address and share it with us. You will get a letter from AWS that you will need to confirm. 

Make it your own. 

1. **Design**. Send us your logo, colours, brand name, relevant web links etc.
2. **Domain**. Add *app.yourcompany.com* and *admin.yourcompany.com* to your DNS settings. 
3. **Data storage**. Inform us whether you want to keep your client data on the servers in the EU or Switzerland. 
4. **Workflow**. Decide on a particular onboarding pipeline for your clients 

Don't be shy and ask for help. Our support team will guide you through the entire process.


---

# 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://help.marketguard.io/marketguard/integration-guide.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.