bidflow-ingest

Name: bidflow-ingest
Availability: InStock
Author: Sihu

Automate ingestion of TED and SAM.gov bid data into a normalized database.

Updated Aug 27, 2026

Search Tags:#pipeline #ingest #data normalization #sam.gov #ted

Ready to run

npx skills add https://github.com/sihu-dev/bidflow --skill bidflow-ingest

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bidflow-ingest
Source: https://github.com/sihu-dev/bidflow/tree/main/.claude/skills/bidflow-ingest
Command: npx skills add https://github.com/sihu-dev/bidflow --skill bidflow-ingest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Manually collecting tender notices from multiple sources is slow and error-prone. This Skill automates ingestion, normalization, de-duplication, and storage for TED and SAM.gov data.

Core Features & Use Cases

Ingest Pipelines: TED and SAM.gov connectors feeding a normalization layer and dedup step.
Normalized Data & DB Storage: Structured normalization of notices for downstream analytics.
Use Case: Run a nightly ingest to populate the database with fresh tenders from TED and SAM.gov.

Quick Start

/sync ted to ingest TED notices; /sync sam_gov --from 2025-01-01 to 2025-01-31

Frequently Asked Questions about bidflow-ingest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate ingestion of tender data from TED and SAM.gov?▼

Automate tender ingestion by setting up connectors to TED and SAM.gov APIs, which parse responses, normalize the data into a structured format, deduplicate entries via content hashing, and persist results to a database. Use /sync ted or /sync sam_gov commands to trigger ingestion workflows.

What does data normalization in a tender pipeline do?▼

Data normalization transforms raw tender notices from multiple sources into a consistent schema with standardized fields. This enables cross-source querying, deduplication by content hash, and reliable downstream analytics on bid data.

Can I ingest tenders from both TED and SAM.gov into a single database?▼

Yes. The Skill supports dual-source ingestion from TED and SAM.gov APIs into one normalized, queryable database. Deduplication via hashing prevents duplicate entries across sources, and CLI commands like /sync ted and /sync sam_gov --from DATE allow scheduled or on-demand syncs.

What are the prerequisites to run tender data ingestion?▼

You need Node.js runtime, access to TED and SAM.gov API endpoints, authentication credentials for each source, and a database to persist normalized bid records. The Skill handles connector setup, query building, and error handling internally.

How do I set up authentication for TED and SAM.gov connectors?▼

Configure API credentials for TED and SAM.gov sources within the connector development layer. The Skill implements built-in authentication setup as part of its connector requirements, enabling secure API queries and response parsing.

What's the best way to deduplicate tender notices across multiple data sources?▼

Implement content-based deduplication using hashing, as this Skill does via a contentHash field in the NormalizedBid model. Hash-based dedup identifies duplicate records across TED and SAM.gov regardless of source format differences.