Gate97Docs
Sign up

Getting started

Gate97 connects the apps you already use — Google Sheets, Slack, Stripe, GitHub, and dozens more — into automated workflows. Pick a trigger in one app, add one or more actions in others, and Gate97 runs it every time the trigger fires. No code required.

Core concepts

  • Connection — one set of credentials for a third-party app (an API key, an OAuth login, etc). See Connections & Auth.
  • Workflow — one trigger step followed by an ordered list of action and filter steps. See Workflows, Triggers & Actions.
  • Run — one execution of a workflow, created every time its trigger fires. Every run records each step's input, output, and status, visible in that workflow's Run History.
  • Task — one action step that completes successfully inside a run. This is the unit your plan is billed and limited on. See Billing & Plans.

Build your first workflow

  1. Sign up. Creating an account also creates your organization — everything in Gate97 (connections, workflows, billing) belongs to an organization, not an individual user.
  2. Connect an app. From Connections, pick an app and authorize it. Apps that use OAuth (Google Sheets, Slack, LinkedIn, X, Instagram) need your organization to register its own OAuth app first — see Connections & Auth for why and how. Everything else just needs an API key.
  3. Create a workflow. From Workflows, click New workflow and give it a name.
  4. Add a trigger step. This is what starts the workflow — e.g. "New Row Added" in a specific Google Sheet, or "New Issue" in a GitHub repo.
  5. Add one or more action steps. Each one runs in order after the trigger fires. Map fields from earlier steps using {{trigger.fieldName}} — see Workflows, Triggers & Actions for the full templating syntax.
  6. Test a step. Every step has a Test this step button that runs it once, for real, against the connected app, and shows the real response — no need to activate the workflow first to see if it works.
  7. Activate. An inactive workflow never runs. Activating starts polling (or registers the webhook) for the trigger step.
  8. Check Run History. Every trigger firing — successful or not — shows up here, with each step's real input and output.

Where to go next

  • Connector Reference — every app you can connect right now, and whether it can trigger a workflow, act within one, or both.
  • Custom Connectors — connect an app that isn't built in, by pointing Gate97 at its HTTP API directly.
  • Batch Collection & Reports — collect records instead of running one at a time, relay them together, and see the results in a dashboard.
  • FAQ — shorter answers to common questions.