It's easy to build a custom CMS integration with the Contently platform. This integration allows you to push data from the platform to your chosen CMS and you can choose to map that data however you'd like on your end. The data includes whatever content and images are in your Contently story and you have the ability to use those how you wish when you receive the data via the custom CMS integration.
Follow the steps below to add a Custom CMS integration to your Contently account.
If you're building an integration into a different system other than your CMS and don't need the benefit of webhooks, please follow these instructions instead.
Note: You will need to be an org admin in order to complete these steps.
1. Log into Contently and navigate to the Integrations page in your Publication settings.
2. To view all of the integrations for your organization, click the "All publications" option in the publication dropdown.
3. Click the "Add Integration" dropdown to add Custom CMS credentials to your publication.
4. Enter a name for your integration. This name will be used to distinguish your integrations from each other. If you know which webhook URL you want to use, you can fill it in now. Click "Save."
5. Choose which publications should be able to push to this CMS. You can share this integration across multiple publications. If you know which webhook URL you want to use, you can also fill it in now. Click "Save."
6. After you click "Save," we will generate your API key and show you a link to our API documentation to help you get started. We'll also email this information to you so that you—or someone else on your team—can start working with our API.
If you'd like to get a jump start, you can find our Contently API Documentation here.
Note: Your new integration will now appear in the list on your Integrations Page in Contently. Visit this page to edit your integration or test the status. You can always access your install guide and API key from this page.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article