Pulses with Agents
Learn how recurring scheduled work can run through a named Agent and its current role, context, and permitted resources.
A Pulse can target an Agent when recurring work should run through a consistent AI role.
The Pulse provides the schedule and recurring instruction. The Agent provides the reusable role, durable instructions, context, and permitted resources available at run time.
Why target an Agent?
Use an Agent-targeted Pulse when the recurring job benefits from a stable operating role.
Examples include:
- a Sales Reporting Agent preparing a weekly pipeline review
- a Recruiting Agent reviewing open hiring activity
- a Support Agent checking recurring support signals
- an Operations Agent preparing a scheduled operational summary
The Agent gives the recurring work a consistent way of operating across runs.
How the pieces fit together
Pulse
Defines the recurring instruction and when it runs.
Agent
Provides the reusable role, instructions, context, Skills, and approved Connections available at run time.
The current live environment determines what the Agent can actually use during each scheduled run.
Create an Agent-targeted Pulse
Choose the recurring job
Write the instruction around the result you want each time the Pulse runs.
Choose the Agent
Select the named Agent whose role matches that recurring work.
Choose the schedule
Use a shared schedule slot or a supported custom cadence.
Review the Agent’s access
Confirm that the Agent has the context, Skills, and Connections the recurring job needs.
Confirm creation
Confirm the future scheduled behavior before the Pulse is created.
The Agent stays live
An Agent-targeted Pulse does not freeze the Agent as it existed on the day the Pulse was created.
When the Pulse runs, the current Agent configuration and live workspace state matter.
That can include:
- Agent instructions
- Agent context
- available Skills
- approved Connections
- Group permissions
- provider-side permissions
- current external data
Changes to those resources can affect future Pulse runs.
Connections still follow permissions
An Agent-targeted Pulse can use Connections available to that Agent when the current permissions allow it.
The schedule itself does not create access.
For example, a weekly Sales Pulse can only use the CRM if the relevant CRM Connection is available to the Agent and the connected account has the required provider permissions.
Learn about giving Agents access to Connections →
Skills can shape the recurring method
An Agent may have access to Skills that help with the scheduled task.
For example, a Reporting Agent could use a reusable reporting Skill when that Skill is available in its current scope.
The Pulse still defines the recurring instruction and timing. The Skill supplies the reusable task method.
Agent target vs Track target
Both are valid Pulse targets, but they solve different needs.
| Target | Use it when |
|---|---|
| Agent | The recurring work should run through a named role and its operating context |
| Track | The recurring work belongs to one ongoing body of work and its Track context |
A Pulse can also run without a target.
Learn about creating a Pulse →
Consequential actions still require confirmation
Running through an Agent does not bypass Giga’s normal confirmation rules.
If a scheduled run reaches an action that requires confirmation, such as sending an external message, sharing a file, granting access, deleting an important record, or making a payment, the applicable confirmation rule still applies.
Example: weekly pipeline review
Imagine a Weekly Pipeline Review Pulse targeting a Sales Reporting Agent.
Agent role
Review sales data and surface meaningful changes clearly.
Connections
Use approved sales systems when they are available.
Pulse schedule
Run weekly.
Pulse instruction
Summarize pipeline movement, risks, and items needing attention.
Each run uses the current Agent configuration and live access available at that time.
Image placeholder
Diagram showing Weekly schedule → Pulse → Sales Reporting Agent → Agent context + Skills + Connections → recurring pipeline summary.