Hobspot webhook issue - node.js

I have developed HubSpot integration using nodejs, I have set a webhook in hotspot as tutorial provided by HubSpot. Now the issue is: webhook is not firing from HubSpot to my server URL, if I test the webhook URL with POSTMan it works fine

I can think of 3 issues that might be causing the problem:
The workflow is not really active.
The workflow is active, but the rules to trigger the workflow are not met.
The workflow is active, but the webhook is not firing successfully. You can check the logs of the workflow by going into its "History" tab.
The workflow is being triggered, but not immediately. This does happen frequently; we have seen times where the workflow takes hours to trigger.

Related

Zap Webhook firing intermittently

I’ve set up a very basic Zap with a vFair trigger.  The trigger uses a Webhook.  The trigger is fired when somebody registers for a specific event in vFair, (there is only one event set up).
The problem is that only a few of the registrations in vFair are triggering the Zap, others do not appear in the Zap history at all.  This makes it very difficult to troubleshoot - from vFair’s side they can show that the webhook has triggered in their logs, but in Zapier there is no record of the record being received.
Can anyone shed any light on how to find the cause and fix it?
We are expecting every event registration in vFair to trigger the webhook and send a record to Zapier, but this only happens intermittently. We could have four even registrations in a space of five minutes, of which two trigger the Webhook and two do not.

DocuSign REST API - pause workflow + webhooks (node.js)

Good afternoon,
I am integrating DocuSign into our business applications (node.js) and have an issue:
Is there a way to use the DocuSign connect webhook to let me know when a workflow is paused? On the admin connect page, I have all possible boxes checked on the connect options - which do not include anything about workflow status (mostly signed/delivered/completed/declined stuff).
My current workaround is to add a customField on the Signer 'pauseAfterSigned' which I check for in the webhook xml. If the signer with that field has Status "Completed" then I know the workflow has been paused. This seems like a lousy workaround :(
We currently don't have an event fired when a workflow is paused as far as I know. So your workaround would have to do for now. Can you please provide more information around your scenario? Perhaps it's something we should consider adding depending on the scenario here. Thank you.

Email if a cron job succeeds on Cronitor

Is it possible to add a setting on Cronitor that sends an email once a cron job succeeds. Right now I only get email if a cron job fails.
This is what i have at the moment :
Alert preferences Failure tolerance Duration alerts
Alert notes
(X) Send alerts any time there is a problem
() Only send alerts if my job has consistently not run when expected...
I tried to email/contact support but now answer from Cronitor yet.
I'm one of the creators of Cronitor. I'm really sorry we somehow missed your support inquiry.
The answer is that, yes, this is possible but you cannot set this up without an API call. After the initial setup is complete (and the new alert rule is added) you can continue managing the monitor from the dashboard.
If you email support#cronitor.io again with specifics I can help you with adding this rule via the API.

Zapier - Create Instant Triggers

I'm using Zapier's CLI developer kit to create some app. But when I create a "new object" trigger, the url supplied in official document looks just like a "get all" trigger:
method: 'GET',
url: 'http://example.com/api/objects'
Seems Zapier won't know when a new object is created instantly, instead, Zapier checking all the objects every 5 mins.
Their plans shows even the most expensive plan can just provide checking every 5 mins.
So how can I create instant triggers? That said, I want to send a request to Zapier every time an object is created in my app.
Using Webhook also called RestHook you can create an Instant Trigger in Zapier.
If your API didn't support Webhooks then first implement webhook in your API
You can found more about the Webhooks at https://realtimeapi.io/hub/rest-hooks/
Here is a Zapier Sample APP with Instant Trigger implemented
https://github.com/zapier/zapier-platform-example-app-rest-hooks
Zapier Documentation about the RstHook
https://zapier.com/developer/documentation/v2/rest-hooks/
You need to use Webhooks if you want triggers to fire instantly.
https://github.com/zapier/zapier-platform-example-app-rest-hooks
Webhooks works greate for such by using catchook zapier method
And Sometimes for time-saving we use email as triggering emails are instant and we send the objects in subject and content then we crop them in parse or formatter

Azure Logic App fails to send message to slack

We have some Logic Apps setup that monitor our various sites and a Slack connection set up. If a non-200 status code is returned, it sends a message to our alerts channel in Slack. We have about 10 sites that are monitored.
The first was setup, tested the cloned for the other sites.
The issue we're having is that they all seem to work bar one.
The site in question was offline this morning (after host updated the server at 3am this morning) and I can in the Azure log the trigger was fired - but no message in Slack.
I changed the Condition to "status equals 200" (to ensure it always fires), ran it manually and still see no message.
As mentioned this logic app was cloned from one that did work so the only thing that changes from app to app is the site URL and the contents of the slack message.
Being relatively new to various Azure features this was a bit of "R&D" for Logic Apps so I'm not really sure what to check.
Any obvious gotchas we should be aware of? Any pointers you can give to help resolve this would be great.
NB: I added Slack API as a tag to this but as this part is handled by Azure and it's working for other Logic Apps feel free to remove.

Resources