@Kamrul Hassan You can use Make for the posting part and LinkedIn credentials—it's just like logging into any regular website, so you won't need to ask users to create API keys, Plus, with Make's free plan, it's more than enough for any user to make several posts per day.

@Scott Weiner Ok, I understand. I was offering the simplest solution for the user, since the Make workflow only required a webhook and the LinkedIn posting module. But what you're trying to do can definitely be done like this: - Each user needs to create their own API Key in the LinkedIn Developer Portal and request the necessary permissions - Register that API Key in your frontend tool - Then in your n8n workflow, handle dynamic variables for the credentials That way, you can use the same workflow to post on behalf of all the users or team members you want. The only other option is to create an app in the LinkedIn Developer portal and use that app to register tokens from users who log into your frontend. Then, use those tokens to post on their behalf. This approach is a bit more complex and requires additional approvals from LinkedIn.

I would recommend Apify. In addition to offering more credits to start with, which is very beneficial if you're doing testing, it also has a wide range of options and use cases.

Hi Haisem, I just used it and it was working fine for me. Could it be something with the internet? Regards.

If you want to use the Gmail Calendar node, for example, you can use dynamic variables for credentials. These variables can be retrieved from a database, so each user who wants to use the calendar would only need to share their credentials once, which you then store in the DB. During execution, you can filter by user to retrieve the correct credentials and pass them to the Calendar node as a variable. This is an effective way to reuse the same node for different users without duplicating the workflow logic.