Get a structured, cited news brief on one company: governance, executives, strategic events, financial situation, and senior HR moves.

This is a workflow tool built on top of Perplexity's Sonar chat/completions API: it fixes the prompt structure and section headings so every call returns a comparable, five-section brief, and maps a plain lookback_days number to Perplexity's recency buckets (there is no native "3 months" filter, so lookback_days=90 is mapped to the nearest bucket, 'month').

Args:

• organization (string): Company name, e.g. "Doctolib".

• lookback_days (number, 1-365, default 90): how far back to search ("90" = "last 3 months").

• language ('fr'|'en'): default 'fr'.

• response_format ('markdown'|'json'): default 'markdown'.

Returns: Markdown: five headed sections (Gouvernance/Governance, Dirigeants/Executives, Événements stratégiques/Strategic events, Situation financière/Financial situation, Mouvements RH/Senior HR moves), each stating "Rien à signaler"/"Nothing to report" if empty, followed by numbered Sources. JSON: { "answer": string (same structured text), "citations": string[], "search_results": [...], "organization": string, "lookback_days": number }

Examples:

• Use when: "Quelle est l'actualité récente de Nexans ?" -> organization="Nexans"

• Use when: weekly veille loop over a list of target companies -> call once per company

• Don't use when: you need sector-wide signals across many companies -> use perplexity_market_signals instead.

Error Handling:

• Returns "Error: ... Invalid Perplexity API key" if PERPLEXITY_API_KEY is missing/invalid (401).

• Returns "Error: ... rate limit exceeded" if too many requests (429).

Find recent, dated market signals (M&A, funding rounds, executive appointments, restructurings, etc.) relevant to a given professional profile and region, as a structured list.

Unlike a free-text Sonar query, this tool constrains Perplexity's response to a JSON schema server-side, so the result is a real array of discrete signals — not markdown you have to re-parse. It returns an empty list rather than fabricated signals when nothing dated and reliable is found; that empty list is itself a meaningful, actionable result (it means the sweep ran and found nothing this period), not a failure.

Args:

• profile (string): Target professional profile, e.g. "CTO groupe / VP Technology / Chief Transformation Officer / Group CIO".

• regions (string[], default ["France","Europe","Luxembourg"]): geographic scope.

• lookback_days (number, 1-30, default 7): how far back to search.

• signal_types (string[], default M&A/levée de fonds/nomination/restructuration): categories.

• language ('fr'|'en'): default 'fr'.

• response_format ('markdown'|'json'): default 'markdown'.

Returns: Markdown: one numbered section per signal (title, type, date, source, summary), or an explicit "no signal found" statement if the array is empty. JSON: { "signals": [{title,type,date,source_url,summary}], "count": number, "lookback_days": number, "regions": string[] }

Examples:

• Use when: weekly sector-wide sweep independent of any specific tracked company

• Don't use when: you already know the company and want its own news -> use perplexity_company_news instead.

Error Handling:

• Returns "Error: ... Invalid Perplexity API key" if PERPLEXITY_API_KEY is missing/invalid (401).

• Returns "Error: ... rate limit exceeded" if too many requests (429).

• If Perplexity returns non-JSON content despite the schema constraint, returns "Error: could not parse signals JSON" with the raw answer included so nothing is silently lost.