Content & Documents · Integration

Abyssale

Add Abyssale to your product for your customers, and give your AI agents governed access to it.

Abyssale generates images from templates through api.abyssale.com with an x-api-key header. Generation is a POST to /banner-builder/{templateId}/generate for a single synchronous image, or to the /async equivalent when you want several formats at once or heavier outputs such as video, GIF, PDF or HTML5. The elements object overrides template layers and its keys are the layer names exactly as set in the template editor, so a designer renaming a layer silently breaks the integration until the mapping is updated. GET /templates/{templateId} is how you discover the current layer names and the available format names such as instagram-post or iab-medium, and it is worth calling rather than hardcoding. Output is a generated file at a returned URL, so downstream storage and retention are your responsibility rather than Abyssale's. fastn keeps each customer's key and template mappings, and handles auth and upkeep as templates evolve.

Start freeBook a demo

In your product

Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.

Let a customer connect their own Abyssale account so generated creative uses their templates and brand, not a generic one

Generate a set of ad formats from one product record so a campaign ships every placement size at once

Render personalised social images per recipient by overriding text and image layers from your own data

Read a template's layers at connect time so your UI offers exactly the fields that template accepts

For your AI agents

Governed, audited access for the agents you build, through the MCP server.

Ask an agent to produce a launch banner in three formats from a product description, returning the generated URLs

Have an agent check which template layers exist before generating, so it never sends an override that will be ignored

Let an agent generate creative on request with each generation audited per tenant against that customer's plan

Example prompt

Generate the spring sale banner in Instagram post and IAB medium sizes with the new headline.

Set up Abyssale in 4 steps

  1. 01Enable the Abyssale connector from your fastn dashboard.
  2. 02Have each customer authorise their own Abyssale account, so calls run under their credentials rather than a shared key.
  3. 03Decide which files, documents and versions your product needs, map those fields, then enable the actions and triggers you want.
  4. 04Call it from your product and expose it to your agents through the same governed connection.

Why teams use the Abyssale integration

What you get by embedding it with fastn instead of building it yourself.

  • Ship an Abyssale integration without building it. Your customers connect their own Abyssale account inside your product and work their files, documents and versions there, with no per-customer code on your side.
  • Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Abyssale update is not your on-call problem.
  • One integration serves your product and your agents. The same governed Abyssale connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.

Used by these teams

MarketingHR & People OpsOperations

Compare with

NotionBoxDocusign

Often used alongside

Tools the same teams tend to run next to Abyssale, across other categories.

ShopifyStripeJiraAsana

Abyssale integration FAQ

How do I add an Abyssale integration to my product?

Enable the Abyssale connector in your fastn dashboard, then let each customer authenticate their own Abyssale account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Abyssale client code in your app and no per-customer branch in your codebase. Setup is 4 steps.

Do my customers each connect their own Abyssale account?

Yes. Every connection is scoped to the individual customer, so each authorises their own Abyssale account and only ever sees their own files, documents and versions. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.

Can AI agents use this Abyssale integration?

Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent to produce a launch banner in three formats from a product description, returning the generated URLs

Who maintains the Abyssale integration?

fastn does. When Abyssale changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.

Whose permissions does the Abyssale integration run under?

Each customer's own Abyssale grant. Where Abyssale holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.

Can my product create or update content in Abyssale automatically?

Where Abyssale supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.

What can I build with the Abyssale integration?

A common starting point: let a customer connect their own Abyssale account so generated creative uses their templates and brand, not a generic one. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.

How much does the Abyssale integration cost?

It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Abyssale does not change your per-connector cost. You can start free with 3 connected accounts.

Add Abyssale to your product

Start free with 3 connected accounts. No sales call required, and no per-customer integration code.

Start freeRead the docs
← All integrations