also, check your date format for the Google query: The after query in Gmail (and the API) uses UNIX timestamp format (in seconds) or the standard date format: 1. Standard Format: after:YYYY/MM/DD Example: after:2024/11/20 will return emails after November 20, 2024. 2. UNIX Timestamp: Gmail API also supports querying with timestamps in seconds since the epoch (not Julian format). Example: after:1700448000 (corresponding to 2024/11/20).

from an AI search: (and not a legal opinion): While scraping publicly available data from LinkedIn is generally considered legal, it is explicitly against LinkedIn's terms of service, meaning they can take action against you for doing so, even if you are accessing publicly visible information on profiles; essentially, scraping on LinkedIn is not illegal but is prohibited by their user agreement and could result in account restrictions or legal action depending on the circumstances. Key points to remember: - LinkedIn's policy:LinkedIn explicitly prohibits scraping data from their platform through their user agreement.https://news.linkedin.com/2022/may/an-update-on-scraping - Public data access:Courts have generally ruled that scraping publicly available information is not illegal. https://www.shrm.org/topics-tools/news/technology/scraping-public-data-linkedin-legal - Potential consequences:https://medium.com/@coryjames.proxycrawl/a-comprehensive-guide-to-linkedin-scraping-legality-and-ethics-234ac15f2887 if you're prepared to spend money, LinkedIn provides tools and services for legitimate data access and usage, such as its API (Application Programming Interface). Using the API allows you to access LinkedIn data while complying with their terms of service and legal requirements.

Without knowing context, i'll give this a stab (the following is pure theory - I haven't tried it myself): @Hung N. for access to workflows you can set up users (some of this may be dependant on the paid version of n8n) and use RBAC to restrict access. Note this needs to be carefully managed with regards to credential management for client aware interactions within a flow ( @Samir Abid) 1. you'll need some form of user registration, and set up a database in n8n with a user key to be able to direct flows. and possibly with encryption of sensitive data 2. you'll need a mechanism for identifying the user in a session. for example if it is Telegram, then user name comes through. If using trigger workflow, you will need to pass some form of identity key with the trigger. 3. if the number of users is low, then you can set up parallel flows with the n8 credentialing. note n8n does not allow credentials to be passed as a variable. 4. if you need a more dynamic flow, then you'll need to restrict yourself to http requests for the users, with and store your credentialling in the database with the user? Although, reading through this doesn't seem robust to me?! There appears to be a couple of paths that are additionally possible. 1. make use of something like LDAP (if we can achieve persistence across nodes. 2. use the CLI to update individual credentials based on the user, and include verification checks before credential execution occurs.

If you're wanting to scrape the whole site, think about querying mysite.com/sitemap.xml and /or pages-sitemap.xml.Then feed those urls into an http request to return the data. You may need some javascript to isolate the urls into a list. You should be able to add this directly to a vector store node with your chosen embedding. On the AIS + Pages there's code and a method to search this live based on a chat search and return to the AI agent so you can hit the latest content dynamically.

@Jan Hoedt if you don't have a valid sitemap then I'd start there with whatever SEO tool you're using. The aim is for your seo to provide sitemap for google indexing. And it also provides the urls for you to scrape. Not all sites have pages-xml but they should have sitemap.xml. can you provide your website url?

depending on your instance of n8n: --------- n8n cloud: https://docs.n8n.io/manage-cloud/set-cloud-timezone/#:~:text=Users%20can%20configure%20the%20timezone,to%20the%20timezone%20you%20want. -------- n8n self-hosted:https://docs.n8n.io/hosting/configuration/configuration-examples/time-zone/ For self-hosted you set it as an environment variable. In my case, I set it as variables for the n8n docker container. I have both TZ and GENERIC_TIMEZONE set. I stop the container, edit the variable and restart. see the attached pic. You can also set them through the command line: https://docs.n8n.io/hosting/configuration/configuration-methods/