Extended Salesforce node configuration for Task and Case fields
Built for Salesforce-heavy n8n users in businesses that require comprehensive Task and Case field mapping for CRM automation..
“For our business use-case, we need some fields in Task and Case resources of salesforce. These fields are missing in n8n. List of the missing fields which would…”
The receipts — real demand
“For our business use-case, we need some fields in Task and Case resources of salesforce. These fields are missing in n8n. List of the missing fields which would be needed - Case - ContactPhone Task - Type TaskWhoIds. It would be great if these fields are supported by n8n.”
Full dossier
Unlock the full dossier — free
Every corroborating quote, the source receipts, and the community echo. One email, no payment.
Why this is a gap
Surfaced from a high-intensity complaint with clear willingness to pay and a specific, reachable audience.
The market
Salesforce-heavy n8n users need Task and Case field coverage for CRM automation workflows. No search volume data but the pain is precise: missing fields block automation.
Competition & the opening
n8n already has Salesforce nodes, but they're incomplete—missing Task ContactPhone, Case fields, and other standard Salesforce objects. Competitors like Zapier and Workato likely have fuller coverage.
What's hard to build
Salesforce's API is large and frequently updated; keeping node coverage in sync requires ongoing maintenance. You also need to test every new field addition against multiple Salesforce orgs to avoid breaking existing workflows.
Why now
No-code automation platforms like n8n have gained adoption but Salesforce node coverage remains incomplete for edge fields.
How you'd monetize
usage-based API or per-integration fee