Outomatiseer tendermonitering met n8n en Activepieces

1. Sign me in yourself. Try this first: you need me only for one approval click.
- If you can send HTTP requests: POST https://app.selltostate.com/api/v1/agent/signup with JSON {"client_name": "<your app name>"}. Show me verification_uri_complete from the reply as a link. I open it, sign up free with Google or email, and approve the code. Every "interval" seconds, POST token_endpoint with {"device_code": "<device_code>"} until the reply has access_token. Send access_token in the x-api-key header to the MCP server https://app.selltostate.com/api/mcp.
- If you cannot send HTTP requests: tell me to add the MCP server https://app.selltostate.com/api/mcp in this app. Its sign-in page also creates the free account. Claude: Customize > Connectors > Add custom connector. ChatGPT: chatgpt.com/plugins > + > Add custom MCP server, choose OAuth. Claude Code: claude mcp add --transport http selltostate https://app.selltostate.com/api/mcp, then /mcp > Authenticate.
2. The tools are free to connect. A free account gets plan_search 3 times a day and search for 2 different searches a day: titles, buyers, status and dates. Amounts, winners and notice links need a plan. Call whoami to see my plan. Read the skill at https://www.selltostate.com/skills/selltostate-tender-automation/SKILL.md.
3. Build an n8n workflow that calls the Sell to State API every morning for new tenders that match <my saved search> and posts each one to <Slack channel or CRM>.

---
name: selltostate-tender-automation
description: Automation with n8n and Activepieces with Sell to State data (government tenders and contract awards from official procurement sources). Use when the user wants a scheduled workflow (n8n, Activepieces, Make, Zapier or a cron job) that sends new tenders to Slack, a CRM or a sheet.
---

# Automation with n8n and Activepieces (Sell to State)

## Access

1. MCP: the server https://app.selltostate.com/api/mcp (OAuth, or the x-api-key of the agent sign-in: POST https://app.selltostate.com/api/v1/agent/signup, the user approves one code). Call `whoami`. `active` false is a free account: `plan_search` and `search` only, 1-2 searches a day.
2. REST: https://app.selltostate.com/api/v1 with the header `x-api-key`. Read the key from `STS_API_KEY` and never print it.
3. No plan yet: the user picks a plan at https://app.selltostate.com/plans, or you run the agent signup in "Get access" of https://www.selltostate.com/skills/selltostate/SKILL.md. The user pays in the browser.

## Task

Build an n8n workflow that calls the Sell to State API every morning for new tenders that match <my saved search> and posts each one to <Slack channel or CRM>.

Ask the user for each value in <angle brackets> before the first call.

## Steps

1. Trigger: a schedule, every morning.
2. Call: an HTTP request `GET https://app.selltostate.com/api/v1/search?scope=tenders&q=<words>&country=<slugs>&accepts_bids=true&published_days=1` with the header `x-api-key`.
3. Keep the `id` values that the workflow already sent, and send only new tenders.
4. Send each new tender to the target (Slack, CRM, sheet) with title, buyer (the part of `sub` before " · "), country, `deadline_at`, value with its currency and `source_url`.
5. No code: save the search and use the webhook or Google Sheets output at https://app.selltostate.com/integrations.

## Rules

- Give `source_url` (the official notice) for each tender and award. The user reads the documents and bids on the official portal.
- Amounts are in the source currency. Do not add amounts in different currencies.
- The data shows awards, not bids. Do not say that a company lost a tender.
- On a 402, show the message and the link to the user, then stop. On a 429, wait `Retry-After` seconds.
- Credit the data: "Data: Sell to State (selltostate.com)".

More skills (open tenders, buyer research, competitor wins, alerts, API reference): https://github.com/getbeton/selltostate-skills