We have been able to move the Freshping zap directly to a webhook following Discord's API documents and inactivated the zap.
In three weeks, we need to activate the RSS to Google Business Zap to push up our presence there. This should be followed by an update to the cloud article that we are using this zap from Zapier.
We have been able to move the Freshping zap directly to a webhook following Discord's API documents and inactivated the zap.
In three weeks, we need to activate the RSS to Google Business Zap to push up our presence there. This should be followed by an update to [the cloud article](/AniNIX/Wiki/src/branch/main/Articles/The_Complicated_Cloud.md) that we are using this zap from Zapier.
This has been successfully working. We do this is with Freshping's Webhook integration, using an Advanced JSON webhook sending the below payload.
```
{
"content": "{text}",
"sender": "Freshping",
"check_id": "{check_id}",
"check_name": "{check_name}",
"check_url": "{check_url}",
"request_location": "{request_location}",
"request_datetime": "{request_datetime}",
"request_timeout": "{request_timeout}",
"response_state": "{response_state}",
"response_status_code": "{response_status_code}",
"response_time": "{response_time}",
"response_summary": "{response_summary}"
}
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
We have been able to move the Freshping zap directly to a webhook following Discord's API documents and inactivated the zap.
In three weeks, we need to activate the RSS to Google Business Zap to push up our presence there. This should be followed by an update to the cloud article that we are using this zap from Zapier.
This has been successfully working. We do this is with Freshping's Webhook integration, using an Advanced JSON webhook sending the below payload.