Summary
When pulling Opportunity data through the Salesforce connector, Account-object fields (Account Name, Account Billing State, etc.) never populate — even when requested in the same get_data call as Opportunity fields, even when the correct Account ID is present on every Opportunity record. We need Account Name (and ideally Billing State) to resolve correctly alongside Opportunity data, either as a native join or through a supported field.
Business need
We’re using the Salesforce connector to generate recurring biweekly pipeline reports for our reps — each report lists a rep team’s largest open opportunities and needs to show which customer account each opportunity belongs to. Right now every report we generate has a blank Account Name column, which makes the report far less useful to the reps reading it. This is the single biggest gap left in an otherwise working integration.
What we’ve tried
Filtering the Account table directly by Account ID. Both eq and in filters on account_id consistently return zero rows, regardless of date range (tested with ranges as wide as 2000–2030) and regardless of which specific, confirmed-valid Account ID we use. Filtering the Account table by account_name (a text field) works fine — it’s specifically the ID-based filter that fails.
Requesting Account fields (account_name, account_billing_state) in the same get_data call as Opportunity fields (e.g. opportunity_id, opportunity_account_id, account_name), filtered on an Opportunity field. The Opportunity fields return correctly; the Account fields come back null on every row, even though opportunity_account_id is populated and a manual cross-check confirms those Account IDs exist and have names.
Creating a custom formula field on the Salesforce connector using lookup(opportunity_account_id, account_id, account_name). The field was accepted and is queryable, but returns null on every row — consistent with #2, since the underlying join between Account and Opportunity data isn’t happening at the source.
For comparison, joining Opportunity to Contact works correctly: filtering the Contact table by contact_id (eq/in) returns the expected row every time, and Contact fields resolve properly. So this appears specific to the Account object, not a general Salesforce join limitation.
Request
Please either:
Fix Account-ID-based filtering on the Account table (account_id with eq/in operators) so it returns matching rows, the same way it already works for Contact, or
Enable Account fields (starting with account_name and account_billing_state) to populate correctly when requested alongside Opportunity fields in the same query, or
If there’s a supported way to do this today that we’ve missed, let us know — happy to be pointed at the right approach.
Happy to provide our connector ID, sample queries, or screen-share to help reproduce this. Thanks for looking into it