The data you can access in Clay from Salesforce is scoped to the OAuth user who created the connection, not your personal Salesforce permissions.
Clay can only pull fields and objects that are accessible to the specific OAuth user account used to establish the Salesforce connection. If you're missing case-related fields, the OAuth user may not have access to those specific fields or objects.
To resolve this, you can create a permission set in Salesforce that grants the OAuth user access to the missing case fields, or have someone with broader permissions recreate the Clay-Salesforce connection.
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in Clay Support.
