Zentra Bid/No-Bid Scoring Agent
Outcome
structure tender fit, deadline risk, missing documents, and clarification questions
Problem solved
- The delivered workflow is scoped to structure tender fit, deadline risk, missing documents, and clarification questions.
Who it is for
bid, proposal, and public-sector sales teams
Exact contents
- CHANGELOG.md
- LICENSE.md
- README.md
- REFUND.md
- SUPPORT.md
- automation/IMPLEMENTATION-GUIDE.md
- automation/config.example.json
- automation/input-schema.json
- automation/n8n-workflow.json
- automation/output-schema.json
- automation/sample-event.json
- automation/smoke-test.json
- automation/workflow-spec.json
- download-manifest.json
- gumroad-product.json
- health-check.json
- output-contract.json
- quality-manifest.json
- rollback.json
- sample-data.json
- smoke-fixture.json
Inputs and outputs
Inputs
- Provide a workflow event containing: event_id, occurred_at, payload.
- Use automation/input-schema.json to validate buyer-specific payload fields before activation.
Outputs
- The workflow output conforms to automation/output-schema.json and includes the documented required fields:
- id: Stable Zapier trigger record identifier.
- title: Public procurement opportunity title.
- tender_id: Stable public procurement identifier.
- source: Public-safe procurement feed label.
- country: Procurement opportunity country code.
- matched_at: Timestamp when the opportunity matched.
- published_at: Public opportunity publication timestamp.
- deadline_at: Opportunity response deadline timestamp.
- score: Normalized buyer match score.
- url: Public opportunity or fixture documentation URL.
- metadata: Public-safe Zapier filtering context.
Formats
- ZIP
- Markdown
- JSON
How it works
- Read README.md and automation/IMPLEMENTATION-GUIDE.md before configuration.
- Import automation/n8n-workflow.json into a non-production workspace, or reproduce automation/workflow-spec.json in a supported platform.
- Configure buyer-owned connections using automation/config.example.json; no credential is supplied in the archive.
- Validate a test event against automation/input-schema.json and automation/output-schema.json.
- Run automation/sample-event.json and complete automation/smoke-test.json before activation.
Compatibility and requirements
- Product-specific scope tags: bid no bid, tenders, scoring, procurement.
- Supported implementation guidance is included for: n8n, Make, Zapier.
- This is a self-serve implementation kit; it remains inactive until the buyer completes the archive smoke checklist.
Real sample or preview
- automation/sample-event.json provides the archive’s documented test-event shape; the required output fields are shown in automation/output-schema.json.
Source provenance and freshness
- Zentra prepared product artifact — Prepared from Zentra-owned product metadata until a route-specific source connector is configured. — Zentra-owned product metadata generated inside the application until an approved route-specific public source is attached.
versioned_release
Version and last verification
Version 1.0.0
Last verified 2026-08-13T13:01:29+02:00
License and permitted use
Use is limited to the rights expressly stated in LICENSE.md in the immutable downloaded archive; this listing grants no additional rights.
Update policy
This is an immutable, versioned fixed download. The archive does not state an automatic update entitlement.
Limitations
- No third-party redistribution restriction detected for prepared metadata-only artifacts.
- No hosted Zentra service, workflow-platform account, credential, messaging credit, or done-for-you implementation is included.
- The buyer must review each destination mapping, source terms, consent, retention, security controls, and consequential action before production activation.
Product-specific FAQ
- Does this archive include workflow-platform credentials or a hosted Zentra service?
- No. The workflow specification declares a self-serve kit with no included credentials.
- Does the imported workflow activate automatically?
- No. The archive declares inactive-by-default activation and requires its smoke-test checklist before use.
Related products and bundle path
- No related product or bundle entitlement is asserted by the immutable archive.
Support boundary
Support is limited to the archive and documentation described in SUPPORT.md. Buyers own external accounts, credentials, integrations, activation, and production decisions.