Skip to content
pulsify
Pulsify
00 / Introduction Menu +

00 / Introduction

Your business logic. Running.

Pulsify runs automations for your Amazon accounts. You describe the rule. Your agent writes the code. Pulsify keeps it running after the conversation ends.

Who does what

  • You own the business policy: when ads should pause, how far a price may move, which products to leave alone.
  • Your agent, such as Claude, Codex or ChatGPT, reads your Amazon data through Pulsify, writes the automation in JavaScript, and tests it with you.
  • Pulsify receives Amazon's events, runs your saved code in a sandbox, checks every change the code asks for, sends the permitted ones to Amazon, and records each decision.

No AI runs inside Pulsify. When an event arrives, the code you saved is what runs. It's yours to read, change, or have your agent explain line by line.

The example in this guide

When a product sells out, its ads keep running and spend on clicks that can't convert. This guide builds one automation that pauses a product's ads when its stock runs out and resumes them when it's restocked.

Start with a question rather than a change. Once your agent is connected, ask:

Find products that are out of stock but still spending on ads. Show me the affected campaigns before changing anything.

Your agent reads your stock and advertising data and answers. Nothing changes until you ask for it. The rest of the guide goes from that answer to a running automation: draft it, test it against a real event, activate it, and check what happened.

What the console is for

The Pulsify console is where you connect Amazon accounts, manage billing, and see what your automations did. It's also where you activate an automation or stop one in an emergency. There's no chat and no code editor. That work happens in your agent.

Where to start