Sometimes there are issues with the execution time of “Code by Zapier” (Limited to maybe 2 mins) as well as the response time for the request (30s maybe). You can re-check how much time the script takes to run to get the results and if it is taking more than the allowed time then you can divide it into two steps.

When testing manually this does not cause issues but when the zap is turned on it does not provide the desired result.

Hi everyone,

I have a Zap that triggers when a new customer is created in Shopify. The flow is as follows:

1. Trigger: New Customer in Shopify

2. Code by Zapier: Runs JavaScript to fetch metafields

3. Zoho CRM: Create Module Entry (Deals)

4. Zoho CRM: Additional Create Module Entry steps for espaço invisível grande

The problem is:

If I remove the Code by Zapier step, the Zoho CRM steps execute correctly.

But if I include the Code by Zapier step (which fetches metafields), then the Zap stops processing after this step, and the Zoho CRM steps never execute.

What I’ve Checked So Far:

The Code step doesn't show any obvious errors.

The JavaScript returns a value (I confirmed via logs).

If the Code step is skipped, everything works fine.
 

If your Zap stops after the Code by Zapier step, even though it shows no error and logs a return value, the issue is likely in how that return is structured. Zapier expects a plain object with key-value pairs it can use in the next steps. If you're returning something like an array or an undefined value, the flow may silently break. Even though the Code step seems fine, it might be returning data in a format that Zoho CRM can't read or map, which stops the Zap from continuing. Try returning a simple object like { key: 'value' } just to test if the Zap flows through. If that works, gradually reintroduce your actual logic to find where it breaks.

This interruption often happens due to API limitations, incorrect metafield keys, or authentication issues with Shopify. The Code Step, which is designed to run JavaScript or Python to manipulate data, may fail if the fetched metafields do not match the expected structure, resulting in a runtime error.

Hi everyone,

I have a Zap that triggers when a new customer is created in Shopify. The flow is as follows:

1. Trigger: New Customer in Shopify

2. Code by Zapier: Runs JavaScript to fetch metafields

3. Zoho CRM: Create Module Entry (Deals)

4. Zoho CRM: Additional Create Module Entry steps for reiki training.

The problem is:

If I remove the Code by Zapier step, the Zoho CRM steps execute correctly.

But if I include the Code by Zapier step (which fetches metafields), then the Zap stops processing after this step, and the Zoho CRM steps never execute.

What I’ve Checked So Far:

The Code step doesn't show any obvious errors.

The JavaScript returns a value (I confirmed via logs).

If the Code step is skipped, everything works fine.
 

If your Zap stops after the Code by Zapier step, even though it shows no error and logs a return value, the issue is likely in how that return is structured. Zapier expects a plain object with key-value pairs it can use in the next steps. If you're returning something like an array or an undefined value, the flow may silently break. Even though the Code step seems fine, it might be returning data in a format that Zoho CRM can't read or map, which stops the Zap from continuing. Try returning a simple object like { key: 'value' } just to test if the Zap flows through. If that works, gradually reintroduce your actual logic to find where it breaks.

When using Zapier's Code step to fetch Shopify metafields, users may encounter an issue where the workflow halts unexpectedly. This often occurs due to improper handling of asynchronous API calls or unhandled errors within the script. Shopify's API requires proper authentication and precise metafield queries, and if the response is delayed, malformed, or returns no data, Zapier may interpret this as a failed step and stop execution.

If your Zap stops after the “Code by zapier” step when fetching Shopify meta fields, even without showing errors, the issue often lies in the structure of the returned data. Zapier requires a plain object with key-value pairs—returning an array, null, or improperly formatted data can silently halt the flow. Just like incorrect input can disrupt BMI calculations on Mein-BMI Rechner, any mismatch in expected meta field output can prevent Zoho CRM from processing the next steps. Try returning a simple object like { key: 'value' } to test the flow, and gradually reintroduce your logic. Also, ensure your API calls are properly handled with await and wrapped in try-catch blocks to avoid timeouts or unhandled errors.

thank you for your suggestion

I'm facing an issue where my Zapier workflow stops after the "Code by Zapier" step that fetches Shopify metafields. Without this step, everything works fine and Zoho CRM updates correctly. The code runs without errors and returns data, but the Zap halts afterward. I suspect the problem is with the data format—Zapier expects a simple object, not an array or undefined value. To cover this, I tested with { key: 'value' } and the workflow continued. Proper formatting and error handling seem key to preventing this issue.