↔

How to Integrate Google Calendar with Ashby

Native vs Make vs n8n vs Relay — setup time, cost & field mapping

Integration Status

Google Calendar (Scheduling) has a native integration with Ashby (HR). This built-in connection handles standard sync scenarios without additional automation tools.

Data Flow Architecture

Google Calendar

→ One-Way

Standard API Latency

Ashby

API Tier

REST API v3

Auth Method

OAuth 2.0

Rate Limits

Standard SaaS Limits

Automate Google Calendar + Ashby with n8n

Free, open-source workflows you can import into n8n in one click — no subscription required.

Try n8n free — open source, self-hostable → Browse all n8n templates

Ready to automate? We have a template for you.

Copy this Google Calendar → Ashby blueprint, open n8n, paste it into the canvas, and your workflow is ready to configure.

google-calendar-ashby-blueprint.json

{
  "name": "Google Calendar → Ashby Sync",
  "nodes": [
    {
      "id": "node-1",
      "name": "Google Calendar Trigger",
      "type": "n8n-nodes-base.webhook",
      "typeVersion": 1,
      "position": [
        240,
        300
      ],
      "parameters": {},
      "credentials": {
        "httpHeaderAuth": {
          "id": "1",
          "name": "Google Calendar account"
        }
      }
    },
    {
      "id": "node-2",
      "name": "Ashby Action",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 1,
      "position": [
        460,
        300
      ],
      "parameters": {},
      "credentials": {
        "httpBasicAuth": {
          "id": "2",
          "name": "Ashby account"
        }
      }
    }
  ],
  "connections": {
    "Google Calendar Trigger": {
      "main": [
        [
          {
            "node": "Ashby Action",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "active": false,
  "settings": {
    "executionOrder": "v1"
  },
  "tags": [
    "integratestack",
    "blueprint",
    "google-calendar",
    "ashby"
  ]
}

Download .json

Open n8n

Frequently Asked Questions

How do I connect Google Calendar to Ashby? ▼

There's no native integration. To connect them, you will need a middleware tool like Make or n8n.

Is the connection between Google Calendar and Ashby secure? ▼

Yes. This integration typically uses OAuth 2.0, meaning you grant permission via a secure login window. You do not need to share your raw password, and you can revoke access at any time from your Google Calendar security settings.

Is the sync one-way or two-way? ▼

This is typically a one-way sync: Google Calendar → Ashby. Changes in Ashby do not sync back to Google Calendar.

Will existing data in Google Calendar sync to Ashby? ▼

Usually, no. Most native integrations are "forward-looking," meaning they only sync data created or updated *after* you activate the connection. To move historical data, you will likely need to perform a one-time CSV export/import manually.

Can I sync custom fields? ▼

Native integration is limited to standard fields. For custom field mapping, use an automation tool.

Can I add approval steps before syncing? ▼

Native integrations can't do this. For workflows that need human review (e.g., "Manager must approve before creating invoice"), use Relay.app.

🗂️

Using Google Calendar and Ashby with other tools?

Build your full stack map — see all connections and gaps at once.

See your full stack →