Hi @tracy-floethyachts 

For us to have context about the error, we will need to see screenshots with how your Zap Step 2 is configured in EDIT mode so we can see the field types/descriptions.

Here are 2 screenshots from step 2. 
 

@tracy-floethyachts 

Try turning the Zap ON and testing live.

Then check your Zap Runs history to see the DATA IN/OUT for each Zap step to help you troubleshoot:

https://zapier.com/app/history/

You’ll want to remove the static “Tracy” value in the First Name field.

You may not want to have the full name value set for both the First Name and Last Name fields.

That’s part of the problem...is that Thrive Themes does’t hold any information so I can’t actually test it with this process. I am working with Thrive on it as well. But I will try the history and let you know what happens. Thank you.

K I tested it with a live zap on a form in thrive themes connected to Zapier… and it looks like it’s still stopping at Step 2. 

By the way this is what Thrive had me check/do and I’ve done it all: 

**** from Thrive Themes *****

There are some reasons why this issue happens when testing the zap. It could be one of the following:
 

• WordPress Permalink settings
• 500 internal server error
• 403 forbidden error
• XML-RPC server accepts POST requests only

For reference, please see https://community.zapier.com/troubleshooting-99/trying-to-connect-wordpress-to-zapier-getting-an-error-parsing-response-error-4438

Please try the following to see if this will fix the issue.

1. Navigate to WordPress > Settings > Permalinks.
2. Save the permalinks without changing anything to regenerate the .htaccess file on your server.
3. Navigate to WordPress > Settings > Writing.
4. Save the writing settings without changing anything.
5. Temporarily deactivate the Wordfence Security plugin to rule out the 403 forbidden error or any security settings on the hosting server.
6. Add a code on your theme's functions.php to allow the xmlrpc.php file to run. See code here https://wordpress.org/support/topic/allow-xmlrpcphp/#post-7079463

Note: You can use a child Thrive Theme Builder to add the code in the functions.php file and avoid deleting it whenever updating the parent Thrive Theme Builder version.
https://thrivethemes.com/docs/creating-a-child-theme-in-thrive-theme-builder/?swpmtx=7785cafdc9e208ed7fa7f8cc5c2ba21c&swpmtxnonce=6d0d3b685c

7. Check the Web and Site address URLs to ensure they use HTTPS instead of HTTP. You can use the Better Search Replace plugin to make a dry run test to see if the database table needs updating for the Web and Site address URLs.

Here's our help guide on how to use the plugin https://thrivethemes.com/docs/fixing-a-mixed-content-error-from-your-site/#e28692-run-a-search-and-replace-on-the-websites-database

On the other hand, could you temporarily share the Zappier account access to help me check which POST request URL is being blocked?

here’s what happened with the live test:
 

@tracy-floethyachts 

The Zap Run error is from the Freshsales CRM step.

Check your Zap Runs details here to see more of the details: https://zapier.com/app/history/

Post screenshots showing the DATA IN for Zap Step 2.

Check the Troubleshooting tab and the Logs tab for more guidance.

Post screenshots of those to give us more context.