Our available source connections in the Data Connection application now include over 150 new supported source types. These new sources allow organizations to access data in even more locations using Palantir-provided JDBC drivers. New source types include DynamoDB, Dataverse, CosmosDB, LDAP, and many others.
Updated Data Connection landing page showing new connectors.
The new sources have been released in the Experimental stage of Palantir’s development life cycle and are labeled as such. Each source will independently follow the stages of the development lifecycle as usage and support expand.
All third-party trademarks (including logos and icons) referenced remain the property of their respective owners. No affiliation or endorsement is implied.
Hi! Can you send a screenshot of the properties you’ve set for this connection? Feel free to redact any sensitive information from the screenshot. Also what is the behavior you are seeing? Are you getting any errors or is there just no rows showing up for any of the tables?
Has anyone got any experience with the Instagram connector? I have managed to create an app in Meta for developers and connect it to foundry, however the only insights I can successfully import are “comments” the others, of which there are many, are visible but then when I click on them to sync them to foundry I cannot see the actual data and get a token null error. There is only one token and it clearly works because I can see the comments, so I would assume the error is somewhere in the meta api but am stuck on how to fix it. Any advice?
Hey Margot, I suspect from the behavior you have described that there may be an issue with your Meta app causing permission errors. Can you share the exact error returned when you attempt to preview a table besides Comments? Additionally, if it loads, can you share a screenshot of the ‘Permissions’ table preview? This table returns the permissions available in the current session.
It sounds like this could be bug. So we can help you further, please file a Foundry Issue with your support team - this will be the best way to get this resolved.
