AtalayaAtalaya

← Back to site

Integrations

Atalaya fits your workflow. Today you can analyse mail from an Outlook add-in, receive alerts in Teams and orchestrate analyses from Power Automate; Microsoft Entra SSO is on the roadmap.

📨 Outlook add-in (optional)

An optional add-in puts an «Analyse with Atalaya» button inside Outlook (desktop and web): open an email, click, and see the verdict without leaving your mailbox. It does not replace the web app or the API — it is added convenience. It only reads the message (ReadItem permission); it never writes to your mailbox.

  1. In Outlook: Get Add-ins → My add-ins → «Add a custom add-in» → «Add from URL».
  2. Paste the manifest URL: the /addin/manifest.xml path of your Atalaya instance.
  3. Open any email → Home tab → «Analyse with Atalaya» button → configure the URL and your API key once.
  4. Click «Analyse this email»: Atalaya checks sender, headers (SPF/DKIM if present), links and attachments, and shows a verdict + verifiable report.

The API key is stored in your mailbox settings (roaming), never shared. Sideload distribution; AppSource publishing when there is demand.

🔔 Microsoft Teams alerts

When an analysis returns a critical verdict, Atalaya can post a card to a Teams channel. Since Microsoft is retiring the «Incoming Webhook» connectors, we use the modern method: a Power Automate (Workflows) flow.

  1. In the Teams channel → … → «Workflows» → template «Post to a channel when a webhook request is received».
  2. Power Automate generates an HTTPS URL. Copy it.
  3. Hand it to the Atalaya operator to configure it for your account (PHISH_USER_WEBHOOKS variable).
  4. Done: SUSPICIOUS/PHISHING verdicts get an Adaptive Card with type, score, target and summary.

We also support the legacy connector (webhook.office.com → MessageCard), Slack and Discord. Format detection is automatic from the URL.

⚙️ Power Automate

Atalaya exposes a REST API you can call from any Power Automate flow (the «HTTP» action or a custom connector).

  1. Authentication: X-API-Key header with your key (issued by the operator).
  2. Endpoints: POST /api/analyze-url (links), POST /api/analyze (email .eml/.msg), POST /api/analyze-qr (image/PDF with QR).
  3. Custom connector: import the OpenAPI from /openapi.json to get typed actions in the flow designer.
  4. Typical case: a flow that, on a reported email, calls Atalaya and opens a ticket if the score exceeds your threshold.

🗺️ On the roadmap

Want to connect Atalaya to your stack?

Get in touch