Workflow examples
See practical examples of reusable multi-step processes that fit the current Workflow model in Giga.
Workflows are useful when a task has several meaningful stages that should run in a consistent order.
The examples below focus on process structure. The live Giga environment determines which Skills, Connections, files, and tools are available during a run.
Account research brief
An Account Research Brief Workflow could turn company research into a consistent sales brief.
Gather account evidence
Collect current company facts and relevant evidence from approved sources.
Evaluate useful signals
Identify the signals, risks, and open questions that matter for the sales team.
Prepare the brief
Return the findings in the team’s expected structure.
Possible runtime inputs:
- company name
- company website
- research depth
An Account Research Skill could provide the detailed research method inside the first step.
Candidate interview brief
A Candidate Interview Brief Workflow could standardize how recruiting prepares for an interview.
Gather candidate evidence
Review the available candidate and role material.
Evaluate against the role
Identify relevant strengths, gaps, and evidence-backed open questions.
Prepare interview focus areas
Return a concise brief with the areas the interviewer should probe.
Possible runtime inputs:
- candidate name
- role
- source URL
A Candidate Screening Skill can carry the reusable evaluation method while the Workflow keeps the ordered process.
Customer issue review
A Customer Issue Review Workflow could give support teams a consistent diagnostic path.
Investigate the issue
Gather the relevant customer context, recent activity, and available evidence.
Determine the next action
Identify the likely resolution or the information still required.
Prepare the response
Draft the response or internal recommendation. Ask for confirmation before any outward-facing action.
A step can use approved Connections when the live environment makes the relevant support or customer systems available.
Document review
A Document Review Workflow could separate analysis from final recommendations.
Understand the document
Identify the purpose, audience, and important claims in the material.
Review against the standard
Apply the relevant review criteria and flag missing information, contradictions, or required fixes.
Prepare findings
Return the issues in a consistent structure, separating required changes from optional suggestions.
A reusable review Skill can hold the detailed standards used in step 2.
Customer renewal review
A Customer Renewal Review Workflow could organize account context before a renewal discussion.
Gather current account context
Collect the current information relevant to the renewal.
Evaluate risks and opportunities
Identify evidence-backed risks, opportunities, unresolved issues, and missing information.
Prepare the renewal brief
Summarize the account state and the questions the team should address.
The Workflow can use live Connections when permitted, but provider access still controls which data and actions are available.
Research report
A Research Report Workflow could turn a broad question into a structured piece of work.
Define the evidence needed
Clarify what needs to be established and what would count as reliable support.
Gather and evaluate sources
Collect relevant evidence and separate strong support from uncertainty.
Create the report
Synthesize the findings into the required structure and clearly mark unresolved questions.
Possible runtime inputs:
- research question
- source URL
- desired depth
Content review
A Content Review Workflow could standardize how marketing content moves from draft to approved recommendation.
Understand the draft
Identify the intended audience, message, and purpose.
Review against company standards
Apply the relevant brand, quality, or factual review method.
Prepare the revision brief
Return the required changes with a concise rationale.
A Brand Review Skill can carry the reusable review standard.
Internal handoff
An Internal Handoff Workflow could turn active work into a concise handoff for another teammate.
Gather the current state
Collect the relevant objective, background, decisions, and current status.
Identify what matters next
Pull out unresolved questions, dependencies, risks, and immediate next steps.
Prepare the handoff
Return a concise handoff with the context the next person needs to continue.
If the work belongs to a Track, the Workflow can draw from the Track context available in the current run.
A useful Workflow pattern
Across these examples, strong Workflows tend to follow a similar shape:
| Stage | Purpose |
|---|---|
| Gather | Collect the information needed for the work |
| Evaluate | Apply judgment, rules, or a reusable Skill |
| Produce | Return the useful work product or recommendation |
Real processes can have more than 3 steps, but this pattern is a good test for whether the Workflow reflects meaningful stages instead of low-level tool actions.
Workflow, Skill, or Pulse?
Use a Workflow when the ordered process should be reusable.
Use a Skill when the task method should be reusable.
Use a Pulse when the defining need is recurring scheduled work. The exact way a scheduled run uses other Giga primitives should follow the current live Pulse capabilities.
Image placeholder
Gallery of Workflow cards showing Account Research, Candidate Interview Brief, Customer Issue Review, Document Review, and Internal Handoff.