Google Services: Video Uploads, Email Sending, Calendar Events, and Ad Campaign Reporting

This workflow automates tasks across Google services (YouTube, Gmail, Google Calendar, Google Ads), replacing manual operations in Google Cloud Console or individual service dashboards, which are labor-intensive and error-prone due to 1-hour access token expirations. It handles OAuth2 authentication, token refresh, video uploads, email sending, calendar event creation, and ad campaign reporting. Key nodes include Manual Trigger for testing, Set for input validation (client_id, client_secret, refresh_token, ads_customer_id), IF for credential and token checks, HTTP Request for token refresh and service-specific operations (youtube, gmail, calendar, ads), and Set for success/error responses. Supports operations like refresh_token, video uploads, email sending, event creation, and ad reports. Ideal for marketing teams or creators managing 5+ campaigns, videos, or schedules, it streamlines cross-service automation, reducing manual effort and ensuring API uptime.\n\nSaves 5-10 hours weekly automating 5+ videos, emails, events, or ad reports, cutting downtime by 90%. Suits small to medium businesses or content creators. Requires Google Cloud Project (free, with OAuth credentials) and n8n cloud ($20/month) or self-hosted (free). Scalable to 100+ operations/day but limited by Google Ads (20,000 calls/day), YouTube (10,000 units/day), and Gmail (1,000 emails/day). No webhook needed unless replacing trigger.\n\nInstall n8n from n8n.io or cloud.n8n.io ($20/month unlimited). Create a Google Cloud Project at console.cloud.google.com, enable APIs (YouTube Data v3, Gmail, Calendar, Google Ads), get client_id, client_secret, and refresh_token via OAuth2 (see https://developers.google.com/identity/protocols/oauth2). Set GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_REFRESH_TOKEN, GOOGLE_ACCESS_TOKEN, GOOGLE_TOKEN_EXPIRES_AT, GOOGLE_ADS_CUSTOMER_ID, GOOGLE_ADS_DEVELOPER_TOKEN in n8n environment variables. Configure HTTP Request for token refresh and service APIs. For Webhook, add Webhook node, set path to ‘google’, and use URL (e.g., https://your-n8n/webhook/google123).\n\nTest manually: Run with service=’youtube’, operation=’upload’, video_title=’Test Video’, verify upload in YouTube Studio, or use service=’ads’ for campaign reports. Common errors: invalid refresh_token (re-authenticate via OAuth), missing scopes (ensure youtube, gmail, calendar, ads.readonly), or rate limits (add Wait node, 1s delay). Deploy by activating; monitor logs. Maintain by storing tokens in a database, scheduling token checks every 45 minutes, and adjusting query parameters for large-scale operations.", "businessValue": "Saves 5-10 hours/week automating Google YouTube, Gmail, Calendar, and Ads tasks", "setupTime": "25-40 minutes", "difficulty": "Intermediate", "requirements": ["Google Cloud Project (free, with OAuth credentials)", "Valid refresh token and ads customer ID", "n8n cloud ($20/month) or self-hosted (free)"], "useCase": "Automating video uploads, email sending, calendar events, and ad campaign reporting"