Customers of both Staffbase Communications Control (formerly dirico) and Presspage now have the possibility to set up an integration between the two platforms, allowing customers to create content in Comms Control and push it to Presspage for publication.
To enable this integration, go to 'Advanced' in your account settings. There you'll have the possibility to create an API token.
Warning:
Clicking the button will show a pop-up with the warning that the full API token will only be shown once, so make sure you copy the token to another location before closing the pop-up.
If you generate a new API token, it will automatically invalidate the old token. If you have already used that token in the Comms Control environment, the integration will no longer work until you add the new token there.
API tokens are connected to your own user and to a single account. This means that your team members will be able to create their own API token without invalidating yours. It also means that if you have multiple accounts within a holding, you may need to create API tokens in each account.
Once you have created your API token, you'll need to log in to Comms Control (formerly dirico) and add this API token in your user settings there. Note that if you generate a new API token within Presspage, you'll need to update it at Comms Control as well.
If you're logged in to Comms Control, you can access their documentation on how to create content in their environment and push it to Presspage.
The content you push to Presspage will be a draft article, giving you the option to make final changes before sharing your content with the world.
This integration is one-way: from Comms Control to Presspage. This means that if you make changes to your content in the Presspage environment, it will not automatically be updated in Comms Control.
Currently, our API only supports this integration with Comms Control. We hope to add more integrations in the future. Our Product team will be happy to speak to you about this.