As with many other platforms, we can let you know when certain actions occur on our platform relating to the content you publish with us. This includes your own actions, such as posting a resource update, or those of others, such as someone purchasing your resource.
There are three ways to subscribe to events produced by BuiltByBit in order to automate your workflows. These include:
Webhooks - receive events via HTTP post requests to your own or supported third-party application Discord actions - send messages in your Discord server from our bot (with embeds support) API Events - poll our JSON API for new events and mark them as complete once handled
All three ways you can receive events share a list of ‘triggers’, which is how you define what events are forwarded to you and for what content. Each trigger can have a filter applied to only forward events for specific content or groups of content (like a specific store or a specific category). Triggers also have a list of placeholders which are available, but their use depends on the specific method of receiving events.
When it becomes clear that we can no longer deliver events to your chose method reliably, we may automatically disable the method, preventing future events from being generated. You’ll receive an onsite alert letting you know this has happened. You’re free to re-enable the method at any time once you’ve resolved the underlying issue.