Combining two data sources into a single database

More details would be beneficial.

However, my general strategy would involve setting up two distinct scenarios, one for each webhook. Upon activation, each scenario would query a stored database (perhaps a datastore) to check for the presence of matching webhook data. If found, it would then write the consolidated data to Airtable. If not, it would store the current data for the subsequent webhook.

Some factors that might influence this approach include:

1. Timing: What is the expected interval between webhook calls? Is the sequence of calls consistent?
2. Volume: What is the expected data throughput?
3. Database Choice: Airtable itself could potentially serve as the database for storing partial data.
4. Single Webhook URL: It might be more efficient to utilize a single webhook URL and incorporate a query parameter to differentiate the source. This could help alleviate potential timing conflicts.

Jim - The Monday Man

Thanks for your feedback!

The fourth solution worked perfectly