Showing results for 
Search instead for 
Did you mean: 
Regular Visitor

LinkedIn, Slack and more connectors showing vanishing support for reading data.

Our clients are using their Flow accounts in conjunction with our platform to aggregate data from various sources. LinkedIn and Slack are two of the most commonly-requested sources, but despite a promising start with the first LinkedIn connector, support for reading data from either of them using Flow seems meagre at best.


Perhaps understandably, Slack, as it is a competing service to Yammer, might place limits on reading of data. According to its documentation, the slack API gives the ability to (at least) read messages, but none of that is exposed in Flow.


LinkedIn is owned by Microsoft. The Linkedin V2 Flow connector documentation allows sharing of articles and posts, and listing of followed companies - nothing to read the list of posts, even from the user's own account. 


Less in-demand, but a symptom of the same problem is To-Do. The old Wunderlist connector made it very easy to read lists and items, but To-Do, Wunderlist's replacement since the Microsoft acquisition, only allows one-way operations. Add, create, and copy into. Nothing that makes it possible to to read To Do tasks. 


PowerBI, another Microsoft product, gives no ability to pull reports via Flow (a very common requirements for users who want to show reports elsewhere than the PowerBI dashboard). And yet, PowerBI makes this possible via the API to non-Flow users! 


Is the strategy for Flow really to connect data, or is ity moving to be more of an ingest platform?

Community Support
Community Support

Hi @YourLocalGP,


In my opinion, Flow is more like a data processing platform, which processes data between different servers and completes some procedural work.

For some connectors, Flow currently does not expose these functions, more restrictions will be lifted in the future, and Flow development will gradually open up more new functions based on user feedback.

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Thanks Lin. I have not used any connectors on Flow that do processing. My main interest is to help our users aggregate their own data.


Thinking just about LinkedIn, is there a reason why Microsoft, the owner of LinkedIn, cannot give Flow users (also Microsoft customers) access to their own data in LinkedIn?


Dynamics and the Dynamics Outlook plugin are able to go much further, and pull data on 3rd parties, so the functionality for this via web services must be there already.

Hi @YourLocalGP,


More server will be supported by MS Flow in the future, there are two Ideas about LinkedIn, you can vote them make it come true:

Idea about LinkedIn connection:

Idea about LinkedIn trigger and actions:

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hi Lin, 


Thanks for the response. 


Sorry if I am not being clear. 


Our users' problems are not with adding more sources; they are with the limitations of existing sources. 


My question is about a trend we see with these sources to move away from being able to read data, and instead only write. 


The two links you have provided both concerning writing data, not reading. 



Helpful resources

Power Automate News & Announcements

Power Automate News & Announcements

Keep up to date with current events and community announcements in the Power Automate community.

Power Automate Community Blog

Power Automate Community Blog

Check out the latest Community Blog from the community!

Users online (3,754)