Why is the 'Add Contact to Campaign' Node Freezing My Salesforce Flow?

Based on the Salesforce node documentation, a few factors could be at play:

1. Unsupported or Incomplete Operation:
   The Salesforce node documentation lists operations such as creating, updating, and retrieving Contacts but does not include a dedicated “Add Contact to Campaign” operation. In Salesforce, adding a contact to a campaign is usually handled by creating or managing campaign member records. If you’re using an operation that isn’t fully supported or expecting metadata that isn’t being returned as expected, the UI might hang while trying to load configuration details.

2. Metadata Refresh Issues:
   When you changed the Campaign in Salesforce, new metadata (or altered metadata) might be returned. The node’s UI may be trying to pull in details (such as available fields or custom field options) and could be struggling with the unexpected structure. This would explain why even a minimal Flow (with just the manual trigger and the problematic node) hangs on the configuration page.

3. Credential/Mappings Mismatch:
   If your Salesforce credentials or object mappings are based on previous Campaign configurations, a change in the Campaign may cause the node to encounter errors when trying to retrieve or validate parameters. Although the self-hosting setup and other components are verified to be working, a mismatch in the expected object layout can still cause the node UI to freeze.

Suggestions for Troubleshooting:

• Verify the Operation:
  Double-check that you are using the correct operation for adding a contact to a campaign. In Salesforce this typically involves creating or updating a Campaign Member record. If possible, switch to an operation that explicitly handles campaign members (or check if a more appropriate operation exists) instead of an “Add Contact to Campaign” placeholder.

• Refresh Metadata:
  Try re-authenticating or refreshing your Salesforce credentials in n8n so that any changes in Salesforce, including updates to Campaign or related objects, are pulled freshly. This sometimes resolves issues where stale or mismatched metadata causes the UI to hang.

• Check Custom Field Configuration:
  If your new Campaign includes custom fields, ensure that those fields are correctly added using the node’s “Additional Fields” > “Add Field” > “Custom Fields” approach. An incorrect or missing configuration here could result in the node failing to load properly.

• Test with a New Salesforce Connection:
  As a diagnostic step, create a new Salesforce credential entry and use it with a test Flow to see if the problem persists. This can help determine if the issue is related to the integration metadata or settings tied to the current credential.

Addressing the operation choice and making sure that the node correctly retrieves the expected metadata after the Campaign change should help resolve the Page Unresponsive / Aw Snap issue.