Pulses
Learn how Pulses run recurring scheduled work through an Agent, a Track, or a standalone scheduled instruction.
A Pulse is recurring scheduled work in Giga.
Use a Pulse when Giga should perform a check or piece of work automatically on a schedule instead of waiting for someone to ask in a Chat.
Video placeholder
Pulses overview video.
What a Pulse contains
A Pulse can include:
- a name
- the instruction Giga should run
- a schedule
- an optional target
The target can be an Agent, a Track, or no target at all.
The exact schedule options and available targets come from the live workspace.
Pulse vs Chat vs Workflow
| Primitive | Best fit |
|---|---|
| Chat | Work that starts when a person asks |
| Workflow | A reusable ordered process |
| Pulse | Work that should happen automatically on a recurring schedule |
| Agent | A reusable AI role that a Pulse can run through |
| Track | An ongoing body of work that a Pulse can run against |
A Pulse answers when should this work run?
A Workflow answers what ordered process should be reused?
Pulse targets
The current Pulse model supports 3 patterns.
Agent
Run recurring work through a named Agent and its current role, context, and permitted resources.
Track
Run recurring work against an ongoing Track and the context available there.
No target
Run the scheduled instruction without attaching it to an Agent or Track.
The live Pulse configuration is the source of truth for which target is currently available.
Scheduling options
The current Pulse model supports:
- shared named schedule slots
- custom schedules
- daily cadence
- weekly cadence
- monthly cadence
- intra-day cadence
A shared schedule slot lets a Pulse use one of the workspace’s existing named times.
A custom schedule gives the Pulse its own cadence.
What can a Pulse do?
The scheduled instruction can ask Giga to perform work using the context and capabilities available when the Pulse runs.
Examples include:
- check a Track for meaningful changes
- prepare a recurring account update
- run a periodic research check
- review a set of current signals
- produce a scheduled summary through an Agent
Access still depends on the live environment. A Pulse does not create new permissions or Connections.
Pulses and Agents
An Agent can be the target of a Pulse.
This is useful when recurring work should run with a consistent role, instructions, context, Skills, and Connections.
For example, a Reporting Agent could run a weekly review through a Pulse when those resources are available in the current workspace.
Learn about Pulses with Agents →
Pulses and Tracks
A Track can also be the target of recurring work.
This is useful when the scheduled task belongs to one ongoing body of work, such as:
- a customer account
- a launch
- a hiring effort
- an ongoing research area
The Pulse can then run with the Track context available at that time.
Track access still matters
Scheduling work against a Track does not widen its audience. The Track continues to follow its Group and permission boundaries.
Live data stays live
A Pulse runs in the environment that exists at execution time.
That means the available:
- Connections
- provider permissions
- Track state
- Agent context
- Skills
- external data
can change between runs.
The Pulse defines the recurring instruction and schedule. Giga still checks the live environment when the work runs.
Creating recurring behavior deserves confirmation
A Pulse causes future work to run automatically.
Giga should confirm the user’s intent before creating one, especially the instruction, schedule, and target.
Deleting a Pulse should also be confirmed.
A simple example
Imagine a Weekly Pipeline Review Pulse.
Schedule
Runs weekly.
Target
Uses the Sales Reporting Agent.
Instruction
Review current pipeline changes and prepare a concise summary.
Live access
Uses the Connections and permissions available when the Pulse runs.
Image placeholder
Diagram showing Schedule → Pulse instruction → optional Agent or Track target → live Giga context and Connections → recurring result.
Explore Pulses
Creating a Pulse
Set up recurring work with an instruction, schedule, and optional target.
Schedules
Understand shared slots and custom recurring cadences.
Pulses with Agents
Run scheduled work through a reusable Agent.
Managing Pulses
Review and change existing recurring work.
Examples
See practical recurring-work patterns.