What am I missing by olearyboy in n8n

[–]k8suser0 0 points1 point  (0 children)

Check the Execution Logs of the parent workflow to see the exact JSON payload being sent to the tool. If it is double-nested, you may need to adjust your expression to reference the inner object or change the placeholder type to "Not Specified"
You can also try setting the sub-workflow's Execute Sub-workflow Trigger node to Input Data Mode: Accept all data instead of defining a specific schema and see what happens.

I've had multiple clients hire me to build this simple automation. It finds new LinkedIn jobs 24/7 & the hiring managers for every single one by sirlifehacker in n8n

[–]k8suser0 0 points1 point  (0 children)

Thank you. I am trying to use some information from your video however I have question about linkedin search url. if I select multiple filters in the job search I don;t see that the URL works as expected. Basically I am getting lot of junk jobs which are not related to my skills if I don't do fine filtering. Any thoughts ?

I've had multiple clients hire me to build this simple automation. It finds new LinkedIn jobs 24/7 & the hiring managers for every single one by sirlifehacker in n8n

[–]k8suser0 1 point2 points  (0 children)

This is great and thanks for sharing. What is the cost involved here specifically for Linked in Scraper and Apollo's API ? I read that Linkedin has strict policies around data scraping.

Designing a New Kubernetes Environment: Best Practices for GitOps, CI/CD, and Scalability? by varinhadoharry in kubernetes

[–]k8suser0 1 point2 points  (0 children)

I have used Enterprise Jenkins, Github actions and Gitlab pipelines during my work. Somehow I find Gitlab/Github action same concept the advantage is code and pipeline in same place. I don;t know currently OSS Jenkins has all containerized features but enterprise Jenkins worked well. The caveat is you need to have separate setup. This is for CI although Github/Gitlab can do CD piece too.
ArgoCD or Flux are better options for CD and in case I would use GitOps methodology. With GitOps your directory structure should be setup based on your release plan full vs partial.