Once submitted, you should receive a Slack notification telling you there has been a new form submission. With the correct URL in place, you could go ahead and test it by responding a Typeform. The last step in fixing this problem is to edit the Typeform webhook endpoint by replacing it with the URL of the server created above. With above code snippet in place, go ahead and deploy the web server - In a development mode, you could use a local tunnel tool like Ngrok to get an SSL secured URL. To solve this problem, we will have to write some code to format the data Typeform provides and send it as a POST request to the Slack URL we got above. Slack expects a specific pattern of JSON data which Typeform does not adhere to. You will notice that Typeform actually sent a response to Slack but Slack was unable to parse this response and send a message to the channel. You will notice that despite submitting a response, you will not receive a slack notification, that sucks! We will get to debugging - click the “view deliveries” button on the specific webhook on the Typeform dashboard. Whenever there is an event flagged under the topic error, a slack notification will be triggered and the event will be posted in the channel. ![]() It consists of a lambda that consumes events from an SNS queue. Fixing Typeform’s JSON Data Pattern for SlackĪt this point, you can go ahead and test the webhook by submitting a form. We have an app hosted in AWS which is connected to a slack channel via incoming webhooks.
0 Comments
Leave a Reply. |