Connect Your Platform
How HarperFlow matches its article fields to your CMS, and what's required vs. optional.
HarperFlow articles are made of named fields: title, body, summary, meta description, FAQs, and more. Mapping tells HarperFlow which field in your own CMS each one should write into.
When you confirm your destination during setup, you choose one of:
Only three fields are required to publish at all: title, slug (the URL segment), and the article body. Everything else, including summary, meta title and description, featured image and its alt text, key takeaways, FAQs, reading time, content type, and topic cluster, is optional. If there's no matching field for one of these, HarperFlow simply leaves it out rather than failing to publish.
HarperFlow suggests a match for each field based on its name and type, and tells you how many it matched automatically. You can review and change any row by hand. A couple of rules apply everywhere: one destination field can only receive one HarperFlow field (you'll see which field is "taken" if you try to double up), and the slug is always locked to your CMS's own built-in slug field rather than something you remap.
Your mapping isn't locked in after setup. From your Site page, use Change where articles go to revisit the same three-way choice and remap fields at any time.
Note: If you rename or delete a field in your collection after setup, HarperFlow's mapping can go stale and publishing pauses until it's re-validated. Check Mapping health on your Site page: usually a single click on Re-validate mapping fixes it, unless the field is genuinely gone, in which case you'll need to remap it.