n8n: scheduled company credit score monitoring workflow

[francescobianco]

Idea

Build an n8n workflow that runs daily, fetches the credit score of a watchlist of companies from Openapi, and sends a Slack alert if any score drops below a threshold.

Pseudocode for the PHP side

use Openapi\Client;

$client = new Client($token);
$watchlist = ['IT01234567890', 'IT09876543210'];

foreach ($watchlist as $vatNumber) {
    $score = json_decode(
        $client->get('https://risk.openapi.com/IT-creditscore', ['cf' => $vatNumber]),
        true
    );

    if ($score['value'] < 40) {
        // trigger Slack webhook from n8n
        yield ['cf' => $vatNumber, 'score' => $score['value'], 'alert' => true];
    }
}

n8n workflow sketch

Cron (daily 8am) → HTTP Request (PHP proxy) → IF score < 40 → Slack message

Open questions

• Is there a way to subscribe to score changes via webhook instead of polling?
• What is the recommended polling interval to avoid burning API credits?
• Would an official n8n workflow template JSON be something the project could ship in examples/n8n/?

[Shahnawaz9493]

Most credit APIs don't support webhooks.

What to Do Instead : -

1. Ask OpenAPI support if they have webhook subscriptions for enterprise.
2. Increase frequency — change Cron from daily to every 6 hours.
3. Add severity levels — different alerts for score < 20, < 30, < 40.
4. Log history — save scores to Google Sheets for trend analysis.

---

How to Import

1. Open n8n → Workflows → Import from File
2. Select credit-score-monitor.json
3. Add these Credentials:
   *apiToken — HTTP Header Auth (OpenAPI token)
   *slack — Slack API (incoming webhook)
4. Edit the Set Watchlist node with your VAT numbers
5. Activate the workflow

[francescobianco]

@Shahnawaz9493 Thanks a lot for the suggestions — especially the severity levels and historical logging ideas, they would make the workflow much more useful in real-world monitoring scenarios.

I also wanted to ask for your opinion about a possible optimization strategy if this feature were implemented directly inside the client.

Do you think the state of score changes could be centralized somehow, using a shared cache layer? For example, if multiple clients are watching the same target company, the fetched results could potentially be reused instead of triggering duplicate API calls every time.

In that scenario, could n8n be used to persist and maintain the state/cache, or would you recommend a more dedicated storage layer for this kind of shared monitoring logic?