Docs · Integrations
CMS Integration
Connect your CMS once. Approve drafts in the AnswerEngine dashboard, click "Mark Live", we push to your CMS automatically. Credentials are AES-256-GCM encrypted at rest.
GitHub PR
Create a fine-grained Personal Access Token
- Visit github.com/settings/personal-access-tokens/new
- Repository access: select the repo we'll PR into
- Permissions → Contents: Read and write
- Permissions → Pull requests: Read and write
- Copy the token (shown once — store in your secret manager)
Configuration fields
| Field | Description |
|---|---|
| token | The token you just generated |
| owner | GitHub org or user name (the part before the slash) |
| repo | Repository name |
| branch | Target branch to merge into (usually 'main') |
| path | Path template — e.g. 'content/blog/{slug}.mdx'. {slug} is substituted. |
Each generated page opens a new PR titled 'AnswerEngine: <page title>'. You merge when ready. Cleanest for engineering teams that want code review before live.
Webflow
Create a Webflow site API token
- Open your Webflow site dashboard
- Site Settings → Apps & integrations → Generate API access token
- Scope: CMS write access to the target collection
- Copy the token
- Note your siteId (from URL) and collectionId (CMS settings)
Configuration fields
| Field | Description |
|---|---|
| token | Webflow API token (v2) |
| siteId | Webflow site ID |
| collectionId | Target CMS collection ID |
| fieldMap (optional) | Map our fields (title, slug, content, schemaTypes) to your collection's field names if they differ from the defaults (name, slug, body, schema-types). |
Items are created as draft (isDraft=true). You publish from the Webflow UI when ready.
Shopify
Create an Admin API access token
- Shopify admin → Apps → 'Develop apps' → Create app
- Configure Admin API scopes → write_pages, read_pages
- Install the app to your store
- Copy the Admin API access token (shown once)
Configuration fields
| Field | Description |
|---|---|
| shop | your-store.myshopify.com (or your primary domain) |
| accessToken | Admin API access token |
| apiVersion (optional) | Defaults to 2025-01 |
| published (optional) | false (default — saved as draft Page) or true (published immediately) |
WordPress
Create an Application Password
- WP Admin → Users → Profile → Application Passwords
- Enter 'AnswerEngine' as the application name
- Copy the generated password (shown once)
Configuration fields
| Field | Description |
|---|---|
| siteUrl | Your WP site URL (e.g. https://example.com — no trailing slash) |
| username | The WP user the application password belongs to |
| applicationPassword | The password generated above |
| status (optional) | 'draft' (default) | 'publish' | 'pending' |
| postType (optional) | Defaults to 'posts'. Use a custom post type slug if needed. |
Custom webhook
Configure a HTTPS endpoint on your own server
- Build an HTTPS endpoint that accepts POST
- Generate a strong shared secret (we recommend 32+ chars)
- On every POST, verify the X-AnswerEngine-Signature header is HMAC-SHA256(body, secret)
- Process the payload — { event: 'cms.push', page: { title, slug, mdxContent, schemaTypes } }
Configuration fields
| Field | Description |
|---|---|
| url | Your HTTPS endpoint |
| secret | Shared HMAC secret (we sign every payload with this) |
12-second timeout per call. We do not retry on failure — your handler should be fast or queue work asynchronously.
Security
- · All CMS credentials encrypted with AES-256-GCM before persist
- · Encryption key (PLATFORM_CMS_ENCRYPTION_KEY) lives only on our servers, never logged
- · Only owners/admins can add or remove CMS credentials
- · Decryption only happens server-side during a Mark-Live action
- · CMS push failure → page does NOT flip to "live" (fail-closed)
