1. Overview
Contentful connector publishes Skayle posts to a chosen Contentful content type. It requires:spaceIdenvironmenttoken(Management API token)contentTypeIdfieldMappingtaxonomyMapping
2. Prerequisites
Before connecting:- Contentful space and environment
- Post content type for Skayle posts
- Taxonomy content types for category/tag/author
- Reference fields on your post content type
3. Creating API credentials
In Contentful:- Go to
Settings -> API keys. - Create a
Content Management APItoken (or Personal Access Token with equivalent rights). - Copy Space ID, Environment, and token.
4. Required permissions
Use a token with read/write management rights. Do not use Delivery API or Preview API tokens for connector publishing.5. CMS-side setup
Create/confirm:- Main post content type (for example
blogPost) - Required fields for title, slug, excerpt, content
- Optional fields for featured image, publish date, status
- Taxonomy content types for categories/tags/authors
- Reference fields in post entries for taxonomy relations
6. Connecting in Skayle
- Open
Settings -> Connector. - Select
Contentful. - Enter Space ID, Environment, and Management token.
- Test connection.
- Select post content type.
- Map Skayle fields to Contentful field IDs.
- Map taxonomy content type IDs.
- Save connector.
7. Field mapping explanation
Required post field mappings:- Title
- Slug
- Excerpt
- Content
- Featured image
- Publish date
- Status
- Published posts are created/updated and then published.
- Draft posts are created/updated and remain unpublished.
- Referenced taxonomy entries must be publishable for parent entry publish to succeed.
8. Publishing test article
- Create a draft in Skayle.
- Assign category/tag/author.
- Publish from Skayle.
- Confirm entry appears under selected content type.
- Confirm referenced taxonomy entries exist and are linked.
- Confirm entry status in Contentful matches expected draft/published state.
9. Common errors & troubleshooting
| Issue | Likely cause | Fix |
|---|---|---|
| Unauthorized token error | Delivery/Preview token used | Replace with Management API token |
| Space or environment not found | Wrong IDs | Verify Space ID and environment name |
| Publish conflict/version errors | Entry version mismatch | Retry publish/update from latest state |
| Failed publish due to references | Referenced taxonomy entries unpublished or invalid | Publish/fix referenced entries and retry |
| Taxonomies not linked | Missing taxonomy mappings or reference fields | Verify taxonomy content types and reference fields |
10. Best practices
- Keep content type field IDs stable after mapping.
- Define taxonomy content types before first publish.
- Validate one post and one update cycle before bulk rollout.
- Keep one connector-specific service token for auditability.