Storage and Notifications

Google Drive and Dropbox

Use Zapier, Make, n8n, or Pipedream to upload the Bannerify url to Drive or Dropbox. Most builders provide an “upload file from URL” action.

S3 and R2

Bannerify supports S3-compatible storage in the createStoredImage and createStoredPdf endpoints. Pass s3Config when you want the file written directly to your bucket.

{
  "apiKey": "key_xxx",
  "templateId": "tpl_xxx",
  "modifications": { "headline": "Stored in R2" },
  "s3Config": {
    "endPoint": "s3.amazonaws.com",
    "region": "us-east-1",
    "bucket": "my-bannerify-renders",
    "accessKey": "...",
    "secretKey": "...",
    "customUrl": "https://cdn.example.com/{key}"
  }
}

modifications can be the API array, object shorthand, or a JSON string. This keeps Zapier, Make, Pabbly, and webhook tools simple because they can pass their native JSON output directly.

Slack

Send a Slack message after rendering. Include the hosted URL, template name, and source record so teammates can audit the output.

WordPress

Use a WordPress media upload action after Bannerify renders the image. Store the returned media ID as the featured image or insert it into a post body.

The WordPress plugin flow adds:

• Settings for a Bannerify project API key and default template.
• [bannerify_image] and [bannerify_pdf] shortcodes.
• Helpers to upload generated files to the WordPress media library.
• A helper to set a generated image as a featured image.

Shopify

Use the generated URL as product media, a banner asset, or a metafield value. For bulk catalog refreshes, run the scenario from product update triggers or a scheduled spreadsheet sync.