By using Zapier with your StoryChief account, you can create custom workflows that trigger when you complete actions.
In this article:
🔔 Note: This help article is a basic guide; N8N has lots of possibilities to tinker with.
Error handling, retry policies etc. won't be covered in this article.
Start connecting to N8N
1. StoryChief as trigger
Step 1. On N8N, create a new workflow. In the workflow, select 'New workflow'.
Click on '+' to add a first step. In the sidebar, choose 'On a webhook call'.
Step 2. Set up the webhook URL to customize the HTTP method, path, authentication and response method.
HTTP Method: POST
Path: Leave as-is or tailor to your preference
Authentication: None
Respond: Using ‘Respond to Webhook’ Node
Step 3. Add an action and choose for "Repond to Webhook". Configure the following fields:
Respond With: JSON
Response Body:
ID: An ID of the content on the platform where it's published
Permalink: A public URL to check that the article is live
Mac: The encryption key from your website (see step 4)
Step 4. In StoryChief, go to the channels, API and choose "Add new destination".
Here, you can paste the webhook URL and retrieve the encryption key for your workflow (optional).
Also check out the help article on how to set up a custom website 👉 Quick link.
🔔 Note: When tinkering with the workflow, use the test URL. When everything is set up, switch the webhook URL to the production URL.
2. StoryChief actions
Prerequisite: In StoryChief, go to the API section and fetch your API key 👉 Quick link.
Step 1. In a new or existing workflow, select "+" to add a new action to the flow. In the sidebar, choose "Core".
Step 2. In the Core options, you will see HTTP Request, which opens a settings modal.
Step 3. In this modal, choose the correct request method (GET, POST, ..) and paste the corresponding URL (see https://developers.storychief.io/).
Depending on the "?includes[]" fields, it's possible to send parameters along.
Alternatively, it's possible to paste the cURL request on the documentation to prefill the fields.
3. Example flows
A. Articles trigger internal flows
Webhook receives article with data
Creates an email/message in your email tool
Responds to StoryChief with the ID, URL & date
Creates a task in Google tasks
B. Send a Slack message when a new article is published
Webhook receives article with data
⚠️ The N8N webhook needs to be selected as an EXTRA website, not as the primary destination
Creates a Slack message to your preferred channel
Fetches the message permalink from Slack
Responds to StoryChief with the ID, URL & date
Slack messages don't seem to have a specific ID, so we used a combination of the channel ID and the timestamp. This is similar to how the permalink is constructed
{
"id": "{{ $json.channel }}/p{{ $('Send a message').item.json.message_timestamp }}",
"permalink": "{{ $json.permalink }}",
"mac": "thisismywebhookkey"
}
