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. You can also choose whether GovTribe emails you when an automation run finishes.

Connected AI clients can also manage automations through GovTribe MCP. Use Create_Automation to create a new automation, Search_Automations to find an existing automation, and Update_Automation to change an automation.

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.

If you are using GovTribe MCP, call Create_Automation with the automation name, prompt, trigger type, trigger configuration, and GovTribe AI project name. To change an existing automation from MCP, find it with Search_Automations, then call Update_Automation with the full updated automation definition.

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

Choose completion email settings

Automations can email you after a run finishes. Today email is the only supported delivery option for automation completion notifications. The email goes to the user who owns the automation and includes a link back to the generated automation conversation.

The text box can also include instructions about the email content, such as what to highlight, how to summarize the result, or what tone to use. For When something specific happens, the text box is required because it defines the condition GovTribe AI should evaluate before emailing you.

From GovTribe MCP, use the flat on_completion_notify_user key with always, conditionally, or never. Use completion_notification_instructions for the condition and email-writing guidance. Do not send internal notification_node or notification_config keys from MCP. When using Update_Automation, omit both completion email fields to keep the current setting, include them to change it, or set on_completion_notify_user to never to turn completion emails off.

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.

Match the trigger and email setting to the job

Use the trigger to decide when the automation should run. Use the email setting to decide whether the automation should behave like a routine recap or a decision alert.

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.

Saved-search to bid/no-bid to annotated outline

Use when: You want GovTribe AI to watch a saved search, qualify new matches, and create or draft annotated proposal outlines only for targets your team should pursue.

Best trigger: Saved search gets new results.

Example saved search: Create a saved search from Federal Contract Opportunities for an active capture lane, then narrow it to buyers, NAICS or PSC categories, set-aside types, vehicles, places of performance, and due-date windows your team can realistically pursue.

Skill language: Use Capture Workflows. Go/no-go is customer-facing wording for the same decision family as bid/no-bid.

Example prompt:

Use Capture Workflows > Saved Search to Bid / No-Bid to Annotated Outline.

Watch the new results from this saved search and qualify them before doing any proposal work. If the automation gives you full result details, use them. If it gives you only GovTribe IDs, retrieve those records before ranking or gating. If the result set is truncated, stale, or includes duplicates, say so.

Assume we are a [business type] with strengths in [capabilities], [vehicles or certifications], [past performance], and [target buyers or geographies]. Treat go/no-go as the same decision family as bid/no-bid. Use BID, BID_WITH_PARTNER, SUB_ONLY, MONITOR_AND_SHAPE, or NO_BID where possible.

Only create or draft an annotated proposal outline for targets that pass the gate as BID or BID_WITH_PARTNER, unless this automation explicitly says to include another threshold. Do not create outlines for weak fits, watch-only records, NO_BID records, monitor-only runs, missing source packages, or targets with hard gate failures.

For each new match, report the gate decision, evidence, outline status, blockers, artifacts created or recommended, and the next capture or proposal action.

Executive gate-review email

Use when: You want leadership to get a short internal pursue, monitor, or pass recommendation instead of opening every generated conversation.

Best trigger: Saved search gets new results.

Best email me setting: When something specific happens.

Useful email instruction: Email me only when a result looks like PURSUE, PURSUE IF TEAMED, BID, or BID_WITH_PARTNER, and keep the email in a short BLUF format for leadership.

Example prompt:

Use Capture Workflows > Conduct Bid / No-Bid Review.

Review the new results from this saved search and produce an internal gate-review recommendation for each serious candidate. If the automation gives you only GovTribe IDs, retrieve the records before deciding. If the result set is truncated, stale, or missing source context, say so.

Assume we are a [business type] with strengths in [capabilities], [vehicles or certifications], [past performance], and [target buyers or geographies]. For each candidate, recommend PURSUE, PURSUE IF TEAMED, MONITOR / WAIT FOR RFP, or NO BID.

Write the output so it works well as an internal email to leadership: start with a BLUF summary, then list the strongest reasons to pursue or pass, the main gate risks, and the immediate next actions.

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.

Recurring capture monitor and pipeline report

Use when: You want a recurring delta report across a market, saved search, pipeline, recompete watch, buyer lane, vehicle, program, NAICS, PSC, geography, or capability lane.

Best trigger: Weekly, daily, saved search gets new results, or pipeline created or updated.

Example prompt:

Use Market Intelligence > Recurring Capture Monitor and Pipeline Report.

Monitor [market, saved search, buyer lane, pipeline, recompete watch, vehicle, program, NAICS, PSC, geography, or capability lane] and tell the capture team what changed. Use the automation trigger context first. If the run provides saved-search result IDs or other GovTribe IDs instead of full records, retrieve those records before summarizing them.

Return a concise report with urgent actions, high-priority new items, watch items, stale pipeline items, timing and deadline risks, missing evidence, and recommended owner actions. Treat the first run as a baseline if no prior run context is available. Hand off bid/no-bid, pursuit qualification, pipeline updates, or proposal amendment review to the right workflow.

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, missing evidence, and the next owner action our team should take.

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.

Compliance and response-plan kickoff

Use when: You want GovTribe AI to turn a new RFI, sources-sought notice, or solicitation package into an immediate response plan with deadlines, checklist items, and owner-ready tasks.

Best trigger: Saved search gets new results for new opportunities, or daily for active proposal targets.

Best email me setting: When something specific happens.

Useful email instruction: Email me only when the run finds a same-day action, a missing required file, a material compliance risk, or a proposal package that is ready for kickoff.

Example prompt:

Use Proposal Workflows > Solicitation Intelligence and Compliance Extraction.

When this automation finds a new RFI, sources-sought notice, or active solicitation that matches our lane, review the source package and pull out the requirements, deadlines, submission instructions, mandatory attachments, page limits, evaluation signals, and compliance risks.

If the source package is complete enough to act on, turn the output into a practical kickoff brief with immediate next steps, owner-ready tasks, open questions, and the proposal or capture actions our team should take first. If important files are missing, say what is missing and stop before acting as if the package is complete.

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.

Price-to-win and pricing pressure alert

Use when: You want an email only when new pricing evidence changes the likely range, increases pricing pressure, or weakens your current assumptions.

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

Best email me setting: When something specific happens.

Useful email instruction: Email me only when the pricing posture materially changes, when a strong comparable appears, or when incumbent or predecessor evidence suggests our current assumptions are weak.

Example prompt:

Use Pricing Data > Pricing Model Workflow.

Review the active pursuits or target records in this automation run and look for pricing evidence that changes how we should position the bid. Use wage baselines, labor-rate benchmarks, comparable awards, line-item evidence, incumbent or predecessor context, and Service Contract Inventory context when it is relevant.

If the new evidence materially changes the likely pricing range, confidence level, staffing assumptions, or pricing pressure, say exactly what changed and what the pricing team should do next. If the new evidence does not materially change the posture, say that clearly.

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, run history, and current notification setting. Generated conversations can be opened from their run history when available.

For MCP-managed automations, use Search_Automations before editing so you can confirm the automation ID, trigger details, state, and recent run history. Update_Automation is a full-definition update: include the updated name, prompt, trigger type, and trigger configuration, not only the one field you want to change.

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.
• Create automation MCP tool: Create automations through GovTribe MCP.
• Update automation MCP tool: Change existing automations through GovTribe MCP.
• Search automations MCP tool: Find automations and recent runs before updating them.
• 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.