Why does the first attempt to deploy triggers in Salesforce always time out, the second one succeeds, but fails to activate upon testing and where can I view triggers for external users in the dashboard?

user-1 · August 25, 2025, 9:01pm

Obviously ChatGPT but yeah

user-1 · August 25, 2025, 9:01pm

Possibly, I have thought this was the issue in the past but no one could confirm

user-1 · August 25, 2025, 9:01pm

Or actually what I thought was that the code needed to be deployed to sandbox first then moved to production somehow (from what I remember)

user-1 · August 25, 2025, 9:01pm

But again, I’m not a Salesforce expert (nor have used it in the past except for this unsuccessful debugging)

user-1 · August 25, 2025, 9:01pm

user-1 · August 25, 2025, 9:01pm

no, unfortunately that’s not it again tried switching the PD env, no success

user-1 · August 25, 2025, 9:01pm

Bummer

user-1 · August 25, 2025, 9:01pm

hi guys, returning to this. As far as I understand, PD is trying to deploy something (an apex class?) to SF. One of the SF guys from my company asked me a very logic question “do you know what it’s trying to deploy?” to which i have no answer, and i can’t find anything that resembles apex code in the pipedream repo. Am I looking in a wrong place? Is there a way to see what PD is trying to deploy into SF?

user-1 · August 25, 2025, 9:01pm

Yeah exactly, the Apex code being deployed can be found in this repo: GitHub - jverce/salesforce-webhooks: Provides an interface to create webhooks in Salesforce for different SObject events

user-1 · August 25, 2025, 9:02pm

that’s fantastic, thank you!

user-1 · August 25, 2025, 9:02pm

user-1 · August 25, 2025, 9:02pm

so this

user-1 · August 25, 2025, 9:02pm

github.com/PipedreamHQ/pipedream

[BUG] Salesforce: New Updated Field on Record triggers broken with certain Object-Field permutations

opened 12:07AM - 19 Dec 23 UTC

malexanderlim

bug blocked triaged

**Describe the bug** Two of our registry Salesforce triggers only appear to be …partially working - specifically, both the webhook and polling version of the trigger "New Updated Field on Record" only work in some cases. Certain object-field permutations fail. 1. New Updated Field on Record (Instant, of Selectable Type) 2. New Updated Field on Record (of Selectable Type) ### To Reproduce Use the account in shared 1P, michael@pipedreamsand... Example workflow with working and broken triggers: https://pipedream.com/new?h=tch_3Z6fVy #### Working Trigger configuration: Contact/title **New Updated Field on Record (Instant, of Selectable Type)** 1. Object Type: Contact Field Type: Title In the Salesforce instance, edit an existing contact, and change the Title. You should see the event fire successfully. <img width="999" alt="Screenshot 2023-12-18 at 3 56 38 PM" src="https://github.com/PipedreamHQ/pipedream/assets/42158621/099b067c-c920-4b10-a6a2-c68d94b92fe1"> #### Broken Trigger configurations Contact/title (polling), contact/email (webhook and polling) 1. The same object/field permutation does not work on the polling version: **New Updated Field on Record (of Selectable Type)** <img width="982" alt="Screenshot 2023-12-18 at 3 59 04 PM" src="https://github.com/PipedreamHQ/pipedream/assets/42158621/dc22b795-7fb6-46db-92ea-6bf2f74f9535"> **New Updated Field on Record (Instant, of Selectable Type)** 2. Object Type: Contact Field Type: Email A nondescript error, ```Error: [object Object] at s._deployWebhook (/var/task/node_modules/salesforce-webhooks/dist/index.js:1:138666) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async s._createWebhookWorkflow (/var/task/node_modules/salesforce-webhooks/dist/index.js:1:138844) at async Object.activate (file:///var/task/user/sources/common-instant.mjs:34:23) at async /var/task/index.js:95:13 at async captureObservations (/var/task/node_modules/@lambda-v2/component-runtime/src/captureObservations.js:28:5) at async exports.main [as handler] (/var/task/index.js:60:20)``` is returned when testing the Contact/Email permutation. <img width="1227" alt="Screenshot 2023-12-18 at 4 02 01 PM" src="https://github.com/PipedreamHQ/pipedream/assets/42158621/4b526d9a-9a1c-4904-9527-48874a7aa44d"> 3. This is also broken with the polling source, as no events fire. **Expected Behavior:** 1. I expect the polling trigger to fire an event when the field that is being watched on an object is changed. 2. I expect the webhook (instant) trigger to return an event for valid permutations, and return a more descript error message if there is something wrong with the setup. **Notes:** The Salesforce setup is complex and somewhat difficult to navigate; I added step-by-step instructions detailing the permissions required to configure webhooks in [our documentation](https://pipedream.com/apps/salesforce-rest-api#getting-started).

user-1 · August 25, 2025, 9:02pm

looks like the problem that i’m seeing

user-1 · August 25, 2025, 9:02pm

and the latest reply is basically “the instant triggers don’t really work, but polling does” which is also consistent with what i’m seeing

user-1 · August 25, 2025, 9:02pm

Maybe we should try the fix since it isn’t working anyway yeah

user-1 · August 25, 2025, 9:02pm

would be hugely appreciated, i’m being pushed around by “polling doesn’t demo well, can you maybe do it every 30 seconds??” which i really don’t want to do

user-1 · August 25, 2025, 9:02pm

can you approve this please: [BUG] Fixed error as reported in Pipedream repo by jcortes · Pull Request #19 · jverce/salesforce-webhooks · GitHub

user-1 · August 25, 2025, 9:02pm

I mean merge

user-1 · August 25, 2025, 9:02pm

Will this fix work for non-string fields? item.{{this}} could be of any time, which would cause deployment issues if at least one of the fields does not accept a value like [default@example.com](mailto:default@example.com)