You can connect Superchat Automations with Zapier using a webhook. This allows you to send data from a Superchat automation to Zapier and trigger workflows in external tools based on automation events.
This setup is useful if you want to continue or extend your automation logic outside of Superchat, for example in CRMs, spreadsheets, task tools, or internal notification systems.
Generating the Webhook URL in Zapier
Firstly, you'll need to log in (or sign up) to Zapier, then select the Webhooks trigger to start the webhook setup in Zapier.
Select Catch Hook as the trigger event to generate the webhook URL in Zapier.
Click on "Copy" to copy the webhook URL which is required in Superchat.
Optional: When configuring this trigger, you may want to enter a Child Key if you wish to receive specific data only. This, however, is not necessary in many cases. Look at our FAQ section at the bottom of this article to understand more about Child Keys and when to use them.
Defining the webhook in Superchat
Now we need to head over to Superchat to configure the webhook automation from that end.
In your Superchat automation, select Zapier via search or scrolling.
Select Trigger a Zap to continue the webhook setup in Superchat.
In the POST section (or whatever Method you have entered for the node) paste in the custom webhook URL that we created in Zapier.
Scroll down to Body and define the names and values you want to send to Zapier.
The Name (left column) determines the field name that will appear in Zapier, while the Value (right column) is filled using Superchat variables - which you can select by clicking the arrow box on the right-hand side of each box.
Scroll down to Response and enter example values for the test variables (this allows us to test that the automation works).
Testing the webhook in Superchat and Zapier
Click on Testing to test the functionality of the Zapier webhook in Superchat.
Once you receive the response Successful Request - 200, you can switch back to Zapier.
Click on Test trigger to test the functionality of the custom webhook in Zapier.
Select a response and check whether the names and variables were correctly sent.
FAQ
FAQ - Child Key
FAQ - Child Key
What is a child key in Zapier?
In Zapier, a child key refers to a nested piece of information found within a larger group of data (often called a parent object). When Zapier receives structured data—like from a webhook or an API—it often organizes related details into "bundles."
Simple Breakdown:
The Parent: A group or category (e.g.,
Customer Details).The Child Key: The specific data point inside that group (e.g.,
Email AddressorPhone Number).
In plain terms: If the incoming data is a "folder," the child keys are the individual "files" inside it. When you're setting up your Zap, you'll see these indented under their parent category, allowing you to pick exactly which specific piece of info you want to use.
What should I write in a Child Key section? Do I put in an API Key?
No, you definitely should not put your API key in the "Child Key" field.
In Zapier, an API key is like a password used for security/authentication. A Child Key is a navigation tool used to find a specific piece of data within a large pile of information.
Here is exactly what you should write in that field:
You should write the exact name (the "key") of the specific piece of data you want to isolate from your test results.
Think of the data Zapier receives as a folder. If you only want the "Email" inside that folder, you tell Zapier to "pick off" that specific child.
If your data looks like this:
{ "user": { "email": "hello@example.com" } }And you only want the email: You would write
email
Do I need to add a Child Key?
No, you do not always need to enter a child key. In fact, most users leave this field blank.
Entering a child key is an optional step that tells Zapier to ignore most of the data it receives and "zoom in" on only one specific section.
When to leave it BLANK (most common):
You want all the data: If you want to use the name, email, and phone number from a webhook, leave it blank. Zapier will parse everything and let you pick those fields in the next step.
Simple data: If the app sending the webhook sends a flat list of info (not buried in deep folders), you don't need a child key.
When to actually USE a child key:
You only use it if the data coming in is "wrapped" in a container you don't want to deal with.
Example Scenario: An app sends you a massive "User Profile" packet, but all the actual data you want is tucked inside a folder called survey_responses.
Without a child key: You’ll have to map fields like
survey_responses.answer_1,survey_responses.answer_2, etc.With
survey_responsesas the child key: Zapier "unwraps" that folder for you. Now, your available fields are justanswer_1andanswer_2. It makes the rest of your Zap much cleaner to build.
Troubleshooting
Troubleshooting
Zapier says “No request found” when I test the trigger — why?
Zapier only shows data after it receives a webhook request. To generate that request, you need to successfully run a test from Superchat. If your Superchat test isn’t completing, Zapier won’t have anything to display yet.
In short: check that the Superchat test is completing.
Superchat shows “An error occurred” when I test the Zapier webhook — what should I do?
This usually means Superchat couldn’t deliver the test request successfully. Common causes include:
The webhook URL is incorrect (copied incompletely, pasted with extra spaces, or outdated - this is usually the issue).
The Zapier trigger step isn’t set to Webhooks by Zapier → Catch Hook.
The Body contains variables that are empty or unavailable in a test context.
Try testing again after verifying the webhook URL and simplifying the Body fields.