Public app homepage

Sajvinder Automation

This website represents the public identity of the Sajvinder Automation workflow. It supports an automated shorts publishing operation and its related channel management processes. The site exists so users, reviewers, and platform partners can clearly understand what the workflow does, who operates it, and where its privacy and usage rules are published.

What this site is

A public website for the Sajvinder Automation app and workflow. It explains the purpose of the workflow, identifies the operator, and provides policy pages required for app trust and verification processes.

What the workflow does

The workflow helps manage repeatable channel operations around short-form content. Depending on the connected services and account permissions, it can assist with content preparation, scheduling, metadata handling, and operational monitoring.

Why this page exists

Reviewers and users need a clear homepage that matches the brand shown in the app configuration. This site keeps the app name, operator identity, privacy policy, and terms in one place.

Workflow overview

The current setup is described as an n8n-based workflow for an automated shorts channel. The public-facing purpose of the app is operational automation for publishing and channel management tasks that the account owner authorizes.

Typical functions

  • Preparing repeatable publishing steps for short-form content.
  • Managing workflow state and task execution in n8n.
  • Using account-authorized platform access only for the features enabled by the operator.
  • Maintaining public documentation for privacy and terms on the same site.

Important note for reviewers

This page is intentionally simple and public. It is designed to make the relationship between the app name, the workflow, and the policy pages immediately clear. The homepage, privacy policy, and terms are all hosted together so that the app identity is consistent across the website and app configuration.

Before using this for Google verification: publish these files on a domain you control, then use that same root domain everywhere in your app setup, including the homepage URL, privacy policy URL, terms URL, authorized domains, and Search Console ownership verification.