✨Notify the start of a live on Slack
Transmit your spot data to your email!
Use Zapier
With Zapier, you can connect MeltingSpot to hundreds of other web services! Automated connections, called Zaps, can automate your daily tasks and create workflows (scenarios) between applications that would otherwise be impossible to connect - all without coding! Each Zap has a trigger, where your information comes from and causes one or more actions in other applications, where your data is sent automatically.
Connecting Zapier with MeltingSpot
Setting up Zapier with MeltingSpot is very easy. No need to code, just follow these steps:
Sign up for Zapier (or log in if you already have an account).
On your Zapier landing page, click on
MAKE A ZAP.Name your zap in the upper left corner.
Choose "Webhook by Zapier" as the application and "catch a Hook" as the event, and click Continue. The event allows you to start a Zap with a specific application. In our case, it is MeltingSpot that manages the tracking of this event so the Zap must simply listen to what MeltingSpot will send it.
In the Trigger part, you can choose which data you want to retrieve. Feel free to look at the data that is sent here. By default, Zap sends all the data.
Retrieve the URL present in the Test part of your Zap
Create your Webhook on MeltingSpot by selecting "Live updated" and using the URL retrieved in the previous point.
Do a Test on the MeltingSpot side.
Then go back to your Zap and click on the "Test trigger" button. The format and details of the data sent will be displayed.
That's it, your Zap is connected with MeltingSpot!
Filtering Webhooks
The "Live updated" webhook is triggered every time the status of a live will update, so every time it goes to Live or Ended status. In this example, we only want the beginning of the lives, so only the webhook whose status field is "Live".
Select "Filter" in the Built-in tools section
Complete your filter with "Live status" as field, "contains" as condition and "Live" as data.
Click on
Continue. This will test your filter. When testing the "Live updated" webhook, the default status that is sent is "Planned". It is therefore normal that the return from your test is "Your Zap would not have continued".
That's it, your filter is in place! Now we need to take care of the action that will be performed when the event happens.
Define the action
Now that your trigger is set up, you can use the information sent by MeltingSpot to Zapier to trigger "actions".
You can perform thousands of different actions with Zapier, such as sending a message. Here's a step-by-step on how to do it with Slack:
Choose "Slack" as the application and "Send Channel Message" as the event, and click Continue. The event allows you to start a Zap with a specific application. In our case, it's MeltingSpot that manages the tracking of this event so the Zap just needs to listen to what MeltingSpot will send it.
Log in to your Slack account (or choose an account already connected to your Zap).
Choose the channel and configure the message you are sending (feel free to integrate the data sent into MeltingSpot thanks to the proposed variables!) and continue.
Test the action to make sure the message is sent correctly on the right channel and with all the characteristics you have assigned to it.
Finally, publish your Zap! Your Zap is now ready!
Dernière mise à jour