Automations (beta)

Click Automations, or open GovTribe AI and choose Automations.

Automations let GovTribe AI run from a saved configuration instead of waiting for you to start every prompt manually. Use automations for recurring research, saved-search monitoring, pipeline review, pursuit follow-up, and other repeatable AI work.

Requirements

Automations require available credits, a project, and a prompt. If credits are not enabled or available for your account, GovTribe may send the account owner to Credits before a new automation can be created.

Projects are required because automations create ongoing work. Keeping them in a project makes the generated conversations easier to find later.

Create an automation

Choose New automation from Automations, then configure the automation.

The automation prompt composer is focused on the saved automation instruction. It is not the same as sending a normal conversation message.

Use schedules

Scheduled automations can run on common recurring patterns or a custom recurrence.

Scheduled runs start at the selected time or shortly after it. Completion time can vary based on the prompt, tools, and amount of work involved.

Custom schedules use RRULE syntax. The selected timezone determines the local time for scheduled runs.

Use event triggers

Event-triggered automations run when supported GovTribe workspace events happen.

GovTribe adds trigger and run context to the automation so the generated conversation can explain what started the run.

Example Automations

Use these examples as starting points for the prompt field. Replace the market, buyer, pipeline, saved search, fit criteria, cadence, and output format with the details that match your team.

Saved-search opportunity triage

Use when: You want GovTribe AI to review new saved-search matches and separate immediate pursuits from lower-priority records.

Best trigger: Saved search gets new results.

Example saved search: Create a saved search from Federal Contract Opportunities for software modernization cloud data engineering, then narrow it to active notices, target agencies, useful NAICS or PSC categories, and set-aside types your team can pursue.

Example prompt:

Use Capture Workflows > Relevant Opportunities.

Review the new results from this saved search and rank them for our capture team. If the automation gives you full result details, use them. If it gives you only GovTribe IDs, retrieve those records before ranking them. If the result set is truncated, say so before the recommendations.

Assume we are a [business type] with strengths in [capabilities], [past performance], and [target geographies or agencies]. For each strong match, recommend pursue, watch, partner, or no-bid. Explain the evidence, timing, likely buyer need, competition risk, and the next action our team should take.

Pipeline health review

Use when: You want a recurring check on whether pursuits in a pipeline are current, well qualified, and in the right stage.

Best trigger: Daily, weekly, or pipeline created or updated.

Example prompt:

Use Capture Workflows > Review My Pipeline.

Review the current pipeline and summarize where the team should focus next. Flag pursuits with stale activity, weak qualification evidence, missing next steps, approaching due dates, unclear owners, or stage mismatches.

Group the output into urgent actions, watch items, and cleanup recommendations. For each item, explain the evidence and recommend a concrete next step the capture team can take this week.

Recompete and follow-on monitoring

Use when: You want GovTribe AI to watch for expiring awards, early notices, forecasts, or new opportunities that may indicate follow-on work.

Best trigger: Weekly or saved search gets new results.

Example saved search: Create a saved search from Federal Contract Opportunities or Federal Forecasts for [program name] [buyer office] recompete follow-on renewal, then narrow it to the buyer, agency, vehicle, incumbent, NAICS, PSC, or geography that defines the market you want to watch.

Example prompt:

Use Market Intelligence > Find Federal Recompete Opportunities.

Look for recompete or follow-on signals in the automation trigger details and any records included with this run. Prioritize records tied to [buyer, agency, office, vehicle, program, vendor, NAICS, PSC, or geography] that may become actionable in the next [timeframe].

If this run includes saved-search results, use those new results first. If only GovTribe IDs are provided, retrieve the records before summarizing them. Identify likely follow-on paths, incumbent or predecessor clues, timing risk, and the next research question our team should answer.

Pursuit stage-change briefing

Use when: You want a short briefing when a pursuit moves into a stage that requires action from capture, proposal, pricing, or leadership.

Best trigger: Pursuit moves stages.

Example prompt:

Use Capture Workflows.

Create a stage-change briefing for the pursuit that triggered this automation. Explain what changed, why this stage matters, and what the team should do next.

Include the pursuit status, buyer and opportunity context, known deadlines, missing evidence, likely risks, recommended owner actions, and questions the team should resolve before moving to the next stage.

Proposal amendment and file-change monitoring

Use when: You want a scheduled check for solicitation updates, amendments, attachments, Q&A, or changed proposal requirements on active targets.

Best trigger: Daily or weekdays.

Example prompt:

Use Proposal Workflows.

Review our active proposal targets in [project or pipeline] for solicitation updates, amendments, attachments, Q&A, or changed proposal requirements since the last run.

Summarize anything that could affect compliance, pricing, technical approach, past performance, due dates, page limits, forms, or submission instructions. For each material change, explain the impact, cite the source context when available, and list the proposal actions the team should take.

Pricing evidence pulse

Use when: You want recurring pricing context for active pursuits or a target market.

Best trigger: Weekly, pipeline created or updated, or pursuit created or updated.

Example prompt:

Use Pricing Data > Pricing Model Workflow.

Review pricing evidence for the active pursuits or target records in this automation run. Look for useful wage, labor-rate, awarded-price, incumbent, predecessor, or comparable-award signals.

Summarize the strongest pricing evidence, gaps that still need research, pricing pressure risks, and a recommended pricing posture for each priority pursuit. Keep the output practical for a capture or pricing lead.

Buyer or agency market pulse

Use when: You want a recurring view of buyer activity, buying patterns, and emerging demand in a target lane.

Best trigger: Weekly or saved search gets new results.

Example saved search: Create a saved search from Federal Contract Opportunities for [agency or office] [capability lane], such as Department of Energy cybersecurity operations, then narrow it to the record types, notice stages, categories, or locations that match your business development lane.

Example prompt:

Use Market Intelligence > Federal Buying Pattern Analysis.

Create a market pulse for [buyer, agency, office, program, geography, NAICS, PSC, or capability lane]. Focus on changes since the last automation run and explain what they mean for business development.

Highlight new opportunities, awards, forecasts, expiring work, active vendors, set-aside posture, likely demand signals, and recommended follow-up actions. If saved-search result IDs are provided, retrieve those records before summarizing them.

Partner, incumbent, and competitor watch

Use when: You want to monitor vendors connected to a buyer, opportunity lane, vehicle, or pursuit strategy.

Best trigger: Weekly or saved search gets new results.

Example saved search: Create a saved search from Federal Contract Awards for [buyer office] [capability lane], such as VA medical center facilities maintenance, then narrow it to target vendors, vehicles, NAICS, PSC, award dates, or places of performance that reveal incumbent, partner, or competitor activity.

Example prompt:

Use Capture Workflows > Likely Bidders.

Watch for partner, incumbent, and competitor signals related to [target buyer, market, pursuit, vehicle, or capability]. Use the automation context and any new saved-search results to identify vendors our team should know about.

For each vendor, explain whether they look like a possible partner, incumbent, competitor, or market signal. Include supporting evidence, recent activity, buyer alignment, teaming or competition risk, and the next action our team should consider.

Manage automation runs

Automation list and detail views can show the automation status, trigger summary, project, next run, last run, and run history. Generated conversations can be opened from their run history when available.

Automation status shows whether an automation is active, paused, broken, scheduled to run soon, complete, failed, or otherwise unable to run. If an automation is missing a project or marked broken, review it before expecting new runs.

Related articles

• Create a conversation: Start the project conversations that automations can work alongside.
• Choose a skill: Choose the right skill for an automation prompt.
• Manage connected tools: Connect official tools, control chat tool selection, and request a custom connector.
• GovCon workflows with GovTribe AI: Use detailed workflow guidance and copyable prompt examples.
• Settings and personalization: Manage settings that can influence AI responses.
• Saved searches: Create saved searches that can trigger automations.