Skip to main content

Help Needed: Zapier Integration Between BigCommerce and Salesforce
I'm trying to set up an integration between BigCommerce and Salesforce using Zapier. Here's what I've done so far:

  • I created a Store-level API account in BigCommerce.
  • I activated a webhook in BigCommerce via Postman.
  • I then set up a Zapier Webhook (Catch Hook) and used the Utilities action event.
  • I configured the input with the webhook response body, which is in JSON format.
  • I'm successfully receiving the data, but it's all coming in raw JSON format, which is not very user-friendly.

What I really need is:

  • When an order is placed in BigCommerce, it should trigger a Zap.
  • The order details should then be saved in Salesforce—specifically, I want to capture and store the User ID, Order ID, and Product Name.

Could some one please help me to guide on how to parse the response properly and map these fields into Salesforce correctly? Let me know if I need to use additional steps like Formatter or Code in Zapier.

Hi ​@Satya prakash 

For us to have more info, post screenshots showing how your Zap steps are outlined and configured in EDIT mode with the field mappings visible.

 

Help links for how to parse raw JSON with a Code step: 

 


Hi ​@Troy Tessalone 
I initially tried to connect BigCommerce to Google Sheets using Zapier. My goal is simple:
When a new order is created in BigCommerce, the order details like User ID, Order ID, and Product Name should be saved in a Google Spreadsheet.

The issue I'm facing is:

  • When I publish the Zap for the first time, the first order gets saved in the spreadsheet correctly.

  • However, after that, new orders in BigCommerce do not get recorded in the sheet at all.

I’ve attached screenshots showing how the Zap steps are outlined and configured in Edit mode, including the trigger and the Google Sheets action.

Can you please help me understand why this is happening and what might be causing the Zap to stop working after the first run?

c9156ebe245651824e86d75c018a4439.png
c11d0f9f1f68ce84fa2dee23f0bf790f.png

77b5fbbce75af6c8f7cc20aa0e5b7774.png

9ba29cff92737fc7c2c2083cb2e87efb.png

208d60fb4ec570fc783278f2c3aadb98.png

40c6ca8830f8cdf16fa3d8f3b5aa0c59.png

08139678ecb51061f74afcd6a5b2dba1.png

This post has been edited by a moderator to remove personally identifiable information (PII). Please remember that this is a public forum and avoid sharing sensitive details.


@Satya prakash 

Zaps work while turned ON for new data going forward.

Make sure to test your Zap after it is turned ON.

Check your Zap Run history details to see the DATA IN/OUT for each step.

The DATA OUT for the GSheet step will include the GSheet Row ID to reference.

Help links for using BigCommerce in Zaps: https://zapier.com/apps/bigcommerce/integrations#help

Also, check your Zap app connections here: https://zapier.com/app/connections

 


Hey ​@Satya prakash! 👋

Just spotted this and think you’re likely running into a bug with the Order Created BigCommerce trigger that was discussed originally over here:

So I’ve added you to the list of affected users. I don’t have any sort of ETA I can provide on when the BigCommerce’s developers will be able to get it sorted but you’ll definitely get an email notification from us once they do. 

As you can see from the other thread, this has been a known issue for quite some time so I wanted to highlight an alternative approach that should help get your Zap working:

  1. Set up a Email Parser to create a unique @robot.zapier.com email address - see our Set up your Email Parser account in Zapier for details.
  2. Enable order email notifications in BigCommerce to go to that email address: https://support.bigcommerce.com/s/article/Order-Notifications?language=en_US#enable
  3. Set the Zap to use the New Email (Email Parser) trigger - see our Trigger Zaps from new parsed emails for details.

  

Since there’s already one topic tracking this bug, I’ll close this thread so everyone can follow updates in one place.

If you need help setting up that alternative approach, feel free to post in the main topic and we’ll be happy to assist. Anyone else who wants to be added to the bug report can also chime in there and we’ll ensure you’re added.