I'm setting up iboss for our dev team's security. We're trying to use its Salesforce integration to sync lead status updates.
But every time a lead is updated in Salesforce, iboss seems to send multiple duplicate events. This floods our internal logging system. Has anyone else run into this? I'm worried about API costs and data consistency.
What's the best way to debug this? Are there specific settings in the iboss connector or Salesforce workflow rules I should check first? A real example of a working configuration would be super helpful.
Check your workflow and process builder rules first. They're the usual cause. Each rule that touches the lead triggers a separate outbound message event.
If you're using iboss's generic webhook connector, you need a deduplication key. Salesforce doesn't provide one by default in its outbound messages.
Quick way to verify: add a timestamp field to your logging. If duplicates have the exact same microsecond timestamp, they're coming from Salesforce in the same payload batch. If timestamps differ by a few ms, it's separate events from different automation rules firing in sequence.
Your alert volume is a real cost. I've seen teams blow through API limits in hours because of this.
Metrics don't lie.