# Call API workaround via Zapier

**URL:** <https://community.glideapps.com/t/call-api-workaround-via-zapier/70011>\
**Category:** Ask for Help\
**Tags:** call-api\
**Created:** [January 25, 2024, 1:27pm UTC](https://community.glideapps.com/t/call-api-workaround-via-zapier/70011 "2024-01-25T13:27:45Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hive\_Admin](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/hive_admin/32/66390_2.png) [@Hive\_Admin](https://community.glideapps.com/u/Hive_Admin)\
**Post date:** [January 25, 2024, 1:27pm UTC](https://community.glideapps.com/t/call-api-workaround-via-zapier/70011/1 "2024-01-25T13:27:45Z")

</div>

Hey Guys,

Hope you are all well! We are working with a customer who is on the Pro Legacy Plan and does not want to upgrade to the business package so we cannot use the Glide Call API.

They have an existing software called MMX which is an insurance solution. We are trying to build a feature that can call the data from MMX (not supported by Zapier) and then bring that data back into Glide tables via Zapier.

I got halfway through the GET webhook but then realised that if the logic is :

New Glide action → GET webhook with Glides CURL ADD ROWS API we wouldn’t be calling any data at all 😂

How would you work around this issue with Zapier?

Appreciate any feedback…

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [January 26, 2024, 12:28am UTC](https://community.glideapps.com/t/call-api-workaround-via-zapier/70011/2 "2024-01-26T00:28:27Z")

</div>

I’m not sure I fully understand. Is it right that what you need is calling the data from MMX, then adding rows into Glide Tables?

---

<div class="post-metadata">

**Author:** ![Hive\_Admin](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/hive_admin/32/66390_2.png) [@Hive\_Admin](https://community.glideapps.com/u/Hive_Admin)\
**Post date:** [January 26, 2024, 7:42am UTC](https://community.glideapps.com/t/call-api-workaround-via-zapier/70011/3 "2024-01-26T07:42:39Z")

</div>

Hey @ThinhDinh Yes exactly. I think I might have found a solution :

On Zapier you can catch a webhook, So I reached out to their team to get them to send a webhook to the Zapier Endpoint URL and then trigger a custom webhook to dump it all in Glide Tables.

Should work no?

Thanks alot!

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [January 26, 2024, 8:12am UTC](https://community.glideapps.com/t/call-api-workaround-via-zapier/70011/4 "2024-01-26T08:12:53Z")

</div>

Yes, that will work. But you won’t be sending a Webhook to Glide, because Glide does not listen for Webhooks.

You need to send a HTTP POST request with a JSON payload with a collection of `add-row-to-table` mutations - one for each row to be added.

In Make we would do this using a JSON module to prepare the payload, and then a HTTP module to make the API call. I don’t know how it’s done in Zapier (I don’t use it), but I know it can be done.

---

<div class="post-metadata">

**Author:** ![Hive\_Admin](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/hive_admin/32/66390_2.png) [@Hive\_Admin](https://community.glideapps.com/u/Hive_Admin)\
**Post date:** [January 27, 2024, 9:49am UTC](https://community.glideapps.com/t/call-api-workaround-via-zapier/70011/5 "2024-01-27T09:49:12Z")

</div>

Ah Okay Perfect Thanks a lot mate!

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\
**Post date:** [February 3, 2024, 9:49am UTC](https://community.glideapps.com/t/call-api-workaround-via-zapier/70011/6 "2024-02-03T09:49:25Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
