*Start here*

# 13 gaps in the EULER help center, and a sample page for each

I read support.eulerapp.com against eulerhq.com, the API Reference and the MCP connector reference, and found 13 things a customer, partner or developer needs that the help center does not yet give them. Each gap has a sample page here, written to sit beside the docs that already exist and link to them.

**Reviewed:** 10 Nov 2026 · **Samples:** 13 · **Status:** SAMPLE - NOT OFFICIAL

## Read this in two minutes

- **Already strong:** PAM and POPS, Webhooks, Forms 2.0, Flows, MCP setup, and the partner guide to submitting a referral. None of them is rewritten here.
- **Biggest gap:** DealFlow AI, a headline feature on eulerhq.com, has no help center article. Its email intake appears only as a form type called "AI Email Parse" inside Forms 2.0.
- **Most expensive gap:** the API & Webhooks collection documents a token API that takes a user's email and password, while the API Reference documents API v1 with revocable, scoped keys. A developer who starts in the help center builds on the older one.
- **Easiest gap to see:** the Change Log, linked as "Release notes", ends on 19 March 2026.

## The 13 gaps

| Gap | Sample page | Reader | What is missing today |
| --- | --- | --- | --- |
| 1 | [Admin quickstart](02-quickstart.md) | New admin | Setup articles exist, but no page puts them in the order that avoids rework. |
| 2 | [DealFlow AI](03-dealflow.md) | Partners, admins | No article carries the name. Pieces sit in Forms 2.0, Inbound Referral Management and the Slack guides. |
| 3 | [Pipedrive data flow](04-pipedrive.md) | Admin, RevOps | Forms 2.0 names Pipedrive as a supported CRM. No Pipedrive article exists. |
| 4 | [Salesforce setup checks](05-salesforce.md) | Admin, RevOps | Three articles explain connecting and data flow. None explains the setup decisions that cause failures, or a fix path. |
| 5 | [Incentives and commissions](06-incentives.md) | Admin, finance | Partner view only. The two incentive systems (1.0 and 2.0) are named nowhere in the help center. |
| 6 | [MDF and CIF funds](07-funds.md) | Admin, finance | Covered only inside AI and MCP articles. No admin setup guide. |
| 7 | [Partner Directory moderation](08-directory.md) | Admin | Partner profile setup and embedding are covered. Moderation and the five profile statuses are not. |
| 8 | [Referral statuses](09-statuses.md) | Admin, support | Status values appear only in the API and MCP references. No page says what each means or what to do. |
| 9 | [Which EULER API to use](10-api.md) | Developer | Two APIs are documented side by side, and nothing says which is which. |
| 10 | [Reseller and AWS Marketplace](11-marketplace.md) | Admin, alliances | Product pages only. No help article. |
| 11 | [Release notes](12-releasenotes.md) | Admins, developers | Change Log ends 19 Mar 2026. API changes announced in the reference never reach it. |
| 12 | [Style guide](13-styleguide.md) | Writers | Product names, casing and title patterns vary from page to page. |
| 13 | [Docs update runbook](14-runbook.md) | Docs, product, support | No visible step between "feature shipped" and "docs changed". Internal playbook. |

## Already strong, linked rather than rewritten

- [Configuring and Monitoring PAM for Partners](https://support.eulerapp.com/en/c/ai-agents/customer-guide-configuring-and-monitoring-pam-for-partners) and [Troubleshooting Partner Access Issues with POPS AI](https://support.eulerapp.com/en/c/ai-agents/troubleshooting-partner-access-issues-with-pops-ai)
- [Webhooks: receive events from EULER](https://support.eulerapp.com/en/c/api/webhooks-receive-events-from-euler)
- [Forms 2.0](https://support.eulerapp.com/en/c/core-euler-features/customization-content/forms-2-0) and [Flows](https://support.eulerapp.com/en/c/core-euler-features/flows/flows)
- [Connecting EULER MCP to Your AI Assistant](https://support.eulerapp.com/en/c/euler-mcp-customers/getting-started), with troubleshooting tables for four clients
- [Submitting a Referral or Registering a Deal](https://support.eulerapp.com/en/c/partner-journey/referrals-and-deals/submitting-a-referral-or-registering-a-deal)
- [How to Use Affiliate Links for Partner Attribution](https://support.eulerapp.com/en/c/affiliate-links/how-to-use-affiliate-links-in-euler-for-partner-attribution)

## Take them: free, in Markdown

Every sample is yours to use, edit and publish, with or without me. Download them all as Markdown, ready to paste into Intercom Articles, Notion or a docs repo. Each page also has its own download link at the top.

[You have them: see README.md for the contents](README.md)

## How every sample is built

- **Research first.** Every behavior comes from a public EULER source: [eulerhq.com](https://eulerhq.com/), [the help center](https://support.eulerapp.com/), the [API Reference](https://api.eulerapp.com/docs), or the [MCP connector reference](https://mcp.eulerapp.com/public/docs). Each page lists its sources and links its related docs.
- **No invented interface.** Where a page needs a menu path, address or label that no public source gives, it carries a **[VALIDATE]** flag instead of a guess.
- **Engineers get statements, not meetings.** Each page ends with a short "Confirm with engineering" list, answered yes, no, or correct me.
- **One job per page,** with the reader, the result and what can go wrong on the first screen, a check after every step, one labelled wrong example, and a next page.
- **Shall and should mean different things.** **Shall** marks what the procedure depends on. **Should** marks a recommendation.

**Limits**

I had no product access, ticket data or search analytics, so "biggest" and "most expensive" are judgments from public pages, not measurements. Every UI path not shown in a public source is flagged.

### About the author

Bachtiar Widyantoro writes technical documentation and B2B technical content. He spent ten years as a field engineer in lightning protection, earthing and SCADA, writing method statements, survey reports and as-built documentation, and running his company's website. He built this set for EULER's Technical Writer role.

Whether or not we end up working together, I just hope this helps in your success.

[bachwidy.site](https://bachwidy.site)
[linkedin.com/in/bachwidy](https://linkedin.com/in/bachwidy)
[hello@bachwidy.site](mailto:hello@bachwidy.site)
[The role](https://euler.breezy.hr/p/3fed85a61e91-technical-writer)

### Next

- Gap 2: [DealFlow AI](03-dealflow.md). The biggest gap: register a deal from an email or Slack.
- Gap 1: [Admin quickstart](02-quickstart.md). From an empty workspace to a first approved referral.

---

*Independent writing sample by Bachtiar Widyantoro (bachwidy.site), November 2026. Not published or endorsed by EULER. Free to reuse and edit. Customer names in examples are fictional. Anything marked [VALIDATE ...] or [CONFIRM ...] is not settled by a public source and needs checking before publishing.*