Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

GenerateBanners

Image generation API for banners and social media posts

CategoryContent And Files
Authenticationbasic
Version0.4.6
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect GenerateBanners with Flows360

Image generation API for banners and social media posts

Use the GenerateBanners connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 1 action and no declared triggers.

Available actions

  • Render Template

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: GenerateBanners
  • Package: @activepieces/piece-generatebanners@0.4.6
  • Exact artifact digest: sha256:d427d9d725f79727067a6791bfb8a26f1f68b5e0eb0bfc0354b45fc1deb1d78e
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

BASIC AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Render Template (render_template), Render a GenerateBanners template Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationbasic
Supported objects1
Supported actions1
TriggersNone published

Authentication

Authentication method: basic

Authentication profiles

connection · basic
  • Username Required
  • Password Required · protected credential

Supported objects

ObjectReadWriteNotes
Render Template Yes No Render a GenerateBanners template

Supported actions

Render Template · Read

Render a GenerateBanners template

render_template · Risk: low · Retry: safe

Inputs

  • template_id · string · Required
  • filetype · string · Required
  • variables · object · Required

Setup

Setup

  1. Add the GenerateBanners connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-generatebanners@0.4.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 1 action and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required GenerateBanners connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-generatebanners@0.4.6 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com