Can iDBQuery consume a webhook or event feed?

It helps to be precise about what a webhook is. A webhook is a push: when something happens, a system sends an HTTP call to a listener you provide. iDBQuery works the other way round, it pulls by querying sources on demand and on a schedule, so it is not itself a webhook endpoint. That is the truthful framing, and there are two clean patterns that get webhook data into iDBQuery.

• Land the events, then connect the landing spot. Point the webhook at a small collector or automation (many teams already do this) that writes each event as a row into a database, warehouse table, or even a Google Sheet. Connect that store to iDBQuery and every event becomes part of your live model.
• Poll the source API instead. If the same events are available from the provider's REST API, iDBQuery's API connector can pull them on a schedule, which is often simpler than standing up a listener.

Either way, once the events are in a queryable place you can ask, in plain language, things like the count of events per hour, the error rate over the last day, or how event volume tracks against releases, with every figure cited to the source rows. And because iDBQuery builds one model, you can join those events to customer, billing, or product data to give them business meaning rather than leaving them as raw logs.