Gate97
Sign up

Getting started

Gate97 is a data bridge between the apps you already use — it moves your data from where it starts to where it needs to be. Robots are what run it: pre-built digital workers, each with one repetitive crossing. A robot connects the apps you already use (Google Sheets, Slack, Stripe, GitHub, and dozens more), waits for its trigger — a schedule, or an event like a new row — and runs its crossing every time. No code required. Under the hood, a robot is a workflow you can open and change on a visual canvas.

Core concepts

  • Integration — an app a robot can work with (Slack, Stripe, your ERP). You add each integration once, with one set of credentials (an API key, an OAuth login), and any robot can then use it. That saved credential set is called a connection. See Connections & Auth.
  • Robot — one trigger step followed by the action and filter steps that run after it, on a visual canvas. Every robot is a workflow underneath, so you can open it and change any step. See Robots, Triggers & Actions.
  • Run — one execution of a robot, created every time its trigger fires. Every run records each step's input, output, and status, visible in that robot's work log (its 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.

Hire your first robot

  1. Sign up. Creating an account also creates your organization — everything in Gate97 (integrations, robots, billing) belongs to an organization, not an individual user.
  2. Connect an app. From Connections, pick an integration 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 robot. From Robots, click New robot and give it a name.
  4. Add a trigger step. This is what sets the robot off — e.g. "New Row Added" in a specific Google Sheet, "New Issue" in a GitHub repo, or a schedule like "every morning at 6:00".
  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 Robots, 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 put the robot to work first to see if it works.
  7. Put it to work. A robot that isn't active never runs. Activating it starts polling (or registers the webhook) for the trigger step.
  8. Check its work log. Every trigger firing — successful or not — shows up in Run History, with each step's real input and output.

Where to go next

  • Integrations — every app you can connect right now, and whether it can set a robot off (trigger), act within one, or both.
  • Custom apps — 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.