Glide API / Webhook difference

[MattLB]

If I want to copy data from one table into another internally within a Glide app would the most effective and sensible means be crafting a JSON payload with < 500 mutations and use Call API to/with the AppID? Any alternatives or downsides.

And if I want to copy data from one Glide App to another Glide App (same table type, different instances) would I create the same JSON payload but send it to a Webhook ingest Workflow which would then call the same Glide API (add-row-to-table) with the JSON payload.

In App-to-App scenario do I need to use a Webhook for ingesting or just the Call API (add-row-to-table)? In other words what is value of a Webhook ingest in this scenario versus Glide API?

Thanks

Matt

[MaximeBaker]

@MattLB

want to copy data from one table another internally within a Glide app would the most effective and sensible means be crafting a JSON payload with < 500 mutations and use Call API to/with the AppID? Any alternatives or downsides

Using webhook, you can loop into 1000 rows. So you would be able to copy 1000 rows at a time (kinda).

@MattLB

And if I want to copy data from one Glide App to another Glide App (same table type, different instances) would I create the same JSON payload but send it to a Webhook ingest Workflow which would then call the same Glide API (add-row-to-table) with the JSON payload.

You could either link the other app table to your first app and loop in it, thus removing the need to put a body or you could send the full 1000 rows to the webhook body call.

@MattLB

In App-to-App scenario do I need to use a Webhook for ingesting or just the Call API (add-row-to-table)? In other words what is value of a Webhook ingest in this scenario versus Glide API?

The Glide API mutations JSON version might probably cost less updates and also be faster!