Dynamic Subscriptions for Webhook Event Type Filtering like Stripe

[nathanclevenger]

No description provided.

[AggressivelyMeows]

Im thinking of offering an API like POST /create

{
  "url": "https://localhost",
  "events": [ "airtable.*.records.created" ]
}

Where Airtable is able to create event in the format of source.optionalSelector.resource.created/updated/deleted e.g. airtable.tableID.records.updated. The reasoning is that if we can reduce the amount of requests we send per event, that would improve performance and decrease wasted bandwidth. Why send events to customers if they dont actually want them.

Since we support wildcard selection, if you want to listen to all events relating to records: airtable.*.records.*
If you want to know about records being updated or deleted, but not created: airtable.*.records.(updated|deleted)

[AggressivelyMeows]

Oh and i forgot to mention but the one thing im going to enforce with the events, is that they must end with either created, updated, or deleted. Might be missing one but i think having the basic CRUD resource markers will make it clear whats going on.

[nathanclevenger]

@AggressivelyMeows I'm not sure if we need to enforce CRUD methods, as there could be other simpler events just like email.received or documents.signed or vehicle.delivered

I think the other thing that's getting at, is that we shouldn't be tightly coupled to any underlying architecture/tech but just generally have a flexible and powerful web hook management mechanism.