Everflow integrationEverflow logo

Everflow integration for AI agents.

Everflow integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Everflow tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.

What your agents can do

Real Everflow actions, managed and audited.

Your user connects Everflow once; your agent can then manage Everflow performance marketing offers, affiliates, webhooks, and reporting — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.

  1. 1

    Your user grants Everflow access once (OAuth) — the token lands in the vault.

  2. 2

    Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.

  3. 3

    Every routed call appends a hash-chained audit record — nothing leaves your infra.

Tools & triggers

Supported Everflow tools.

44 tools are generated from the published Everflow catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.

Showing 44 tools. All published catalog entries are included in this page's server-rendered HTML.

Delete Webhook
Permanently delete a webhook configuration by its ID.
Webhookswebhooks
List All Offers
List All Offers
Advertiser Offersadvertiser-offers
Get Offer By ID
Get Offer By ID
Advertiser Offersadvertiser-offers
Find All Visible Offers
Find All Visible Offers
Affiliate Offersaffiliate-offers
Find Offer By ID
Find Offer By ID
Affiliate Offersaffiliate-offers
Find Impression URL
Find Impression URL
Affiliate Offersaffiliate-offers
Find Tracking URL
Find Tracking URL
Affiliate Offersaffiliate-offers
Find All Runnable Offers
Find All Runnable Offers
Affiliate Offersaffiliate-offers
Get Affiliate by ID
Get Affiliate by ID
Affiliatesaffiliates
Get Offer by ID
Get Offer by ID
Offersoffers
Get Click by Transaction ID
Get Click by Transaction ID
Reportingreporting-clicks
Get Conversion by ID
Get Conversion by ID
Reportingreporting-conversions
Get Conversion Upload by ID
Get Conversion Upload by ID
Reportingreporting-conversions
Get Webhook Config
Get Webhook Config
Webhookswebhooks
Get Webhook Delivery Logs
Get Webhook Delivery Logs
Webhookswebhooks
Apply Affiliate Bulk Edit
Apply Affiliate Bulk Edit
Affiliatesaffiliates
Process Pending Affiliates
Process Pending Affiliates
Affiliatesaffiliates
Update Conversion Status
Update Conversion Status
Reportingreporting-conversions
Update Conversion Status by Transaction ID
Modify the status of all conversions and events linked to a single transaction ID. Only `approved` and `rejected` are accepted values. Conversions that are `invalid` will be ignored; only `approved`, `rejected`, and `pending` conversions will be updated. Note that the endpoint is asynchronous. Even when the endpoint returns `true` immediately, it may take up to a few seconds for the conversion updates to be processed (and to fire partner pixels if appropriate).
Reportingreporting-conversions
Find Offers (Advanced)
Find Offers (Advanced)
Affiliate Offersaffiliate-offers
Create Affiliate
Create Affiliate
Affiliatesaffiliates
Find Affiliates (Advanced)
Find Affiliates (Advanced)
Affiliatesaffiliates
Create Offer
Create Offer
Offersoffers
Find Offers (Advanced)
Find Offers (Advanced)
Offersoffers
Get Reporting Summary
Get Reporting Summary
Reportingreporting-aggregated
Get Aggregated Reporting Data
Get Aggregated Reporting Data
Reportingreporting-aggregated
Get MTTI Report
Get MTTI Report
Reportingreporting-aggregated
Search Post-Conversion Events
Search Post-Conversion Events
Reportingreporting-aggregated
Get Variance Report
Get Variance Report
Reportingreporting-aggregated
Get Click Report
Get Click Report
Reportingreporting-clicks
Create Conversions without Transaction IDs
Create Conversions without Transaction IDs
Conversion Updatesreporting-conversions
Create Conversions with Transaction IDs
Create Conversions with Transaction IDs
Conversion Updatesreporting-conversions
Get Conversion Report
Get Conversion Report
Reportingreporting-conversions
Search Conversions by Email
Search Conversions by Email
Reportingreporting-conversions
Get Conversion Summary
Get Conversion Summary
Reportingreporting-conversions
Upload Conversions CSV
Upload Conversions CSV
Reportingreporting-conversions
List Conversion Uploads
List Conversion Uploads
Reportingreporting-conversions
Create Webhook
Create Webhook
Webhookswebhooks
Update Affiliate
Update Affiliate
Affiliatesaffiliates
Update Offer
Update Offer
Offersoffers
Update Conversion Notes
Update Conversion Notes
Reportingreporting-conversions
Update Conversion Payout and Revenue
Update Conversion Payout and Revenue
Reportingreporting-conversions
Update Conversion Sale Amount
Update Conversion Sale Amount
Reportingreporting-conversions
Update Webhook
Update Webhook
Webhookswebhooks
FAQ

Everflow integration, answered

How do AI agents use Everflow through Open Connector?
Your user connects Everflow once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Everflow tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a Everflow MCP server?
Yes. Open Connector can serve Everflow as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Everflow actions with credentials injected server-side.
Where do Everflow credentials live?
In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Give your agents Everflow — keep the keys.

Open source, self-hostable, with Everflow credentials that never leave your infrastructure. Run it from source today.