Oh nice I’ll give it a try later hanks
Posted thread to Discourse: Salesforce Trigger 500 Error: How to Debug?
FYI…this workaround is not optimal at all. I did all of the steps but the JSON that it gets from the XML SOAP body is basically unsuable. I’m just going to use the polling one.
@U02S7FH4T89 so the Instant Salesforce Triggers just don’t work at all then? You either have to do this huge workaround involving salesforce flows and XML to JSON conversions or use polling.
Given how important salesforce is for most company’s this seems really suboptimal.
Andrew, I didn’t follow this thread closely, but is there anything unique to Pipedream that we’re asking users to do? Or are the required steps also a factor for Zapier, Make, etc?
we have a set of instructions on our Pipedream Salesforce app page and I had instructed Jerry to follow them and see if it would fit his use case.
sorry that the workaround doesn’t fit your needs.
We do support JSON webhooks in Salesforce, as shown in the test image below.
We have had issues with another client before, and it was a permission issue. I understand you are the admin for the workspace, but let’s try revisiting this topic
We need to make sure the your Pipedream OAuth app has permissions for deploying Apex Classes and Functions
Can you go to Setup → Platform Tools → Apps → Connected Apps → Connected Apps OAuth Usage → Pipedream → Manage App Policies and share the info in that page?
Also can you share what’s in Setup → Platform Tools → Custom Code → Apex Triggers
Let me give it a try!
Thanks, permissions for the Pipedream integration looks ok.
Looks like the Apex Trigger wasn’t created, though. Should have looked something like this:
Let’s investigate why
hang on looks like there is more
If there’s a way to filter by SW_ prefix, that would be good
created a filter view
there is none that start with SW_
Good to know, thanks. So that’s what is causing the issue. The custom webhook code is not being deployed for some reason.