# Brandiseer Blog > Practical tips for small businesses and marketing teams who use AI for posts, ads, and product photos. ## Agent resources - Use-case catalogue: https://blog.brandiseer.com/use-cases/index.json - Use-case directory: https://blog.brandiseer.com/use-cases - Brandiseer developer documentation: https://brandiseer.com/developers/docs - Brandiseer MCP endpoint: https://brandiseer.com/api/mcp ## Runnable use cases ### Airtable record visuals - Outcome: An agent generates on-brand stills with Brandiseer for Airtable records (campaign cards, product thumbs, content calendar covers, launch creatives); a person then attaches those files in an Airtable attachment field, or an agent with an Airtable personal access token writes the public imageUrl into that field. Brandiseer does not create Airtable bases and does not sync records by itself. - HTML: https://blog.brandiseer.com/use-cases/airtable-record-visuals - Markdown: https://blog.brandiseer.com/use-cases/airtable-record-visuals/agent.md - JSON: https://blog.brandiseer.com/use-cases/airtable-record-visuals/guide.json ### Always-on creative automation - Outcome: Zapier, Make, or n8n triggers generate on-brand stills via Brandiseer REST and deliver image URLs downstream (Drive, Slack, Sheets, CMS, email tools). - HTML: https://blog.brandiseer.com/use-cases/always-on-creative-automation - Markdown: https://blog.brandiseer.com/use-cases/always-on-creative-automation/agent.md - JSON: https://blog.brandiseer.com/use-cases/always-on-creative-automation/guide.json ### EmailOctopus newsletter automation - Outcome: An agent generates on-brand newsletter heroes and promo stills with Brandiseer, and optionally drafts subject line, body copy, and paste-ready HTML; a person places the assets in EmailOctopus and sends. Brandiseer does not create or send EmailOctopus campaigns. - HTML: https://blog.brandiseer.com/use-cases/emailoctopus-newsletter-automation - Markdown: https://blog.brandiseer.com/use-cases/emailoctopus-newsletter-automation/agent.md - JSON: https://blog.brandiseer.com/use-cases/emailoctopus-newsletter-automation/guide.json ### Framer site visuals - Outcome: An agent generates on-brand Framer heroes, section stills, and CMS images with Brandiseer; a person (or a Framer External Agent / plugin) then places those image URLs in Framer Assets, on the canvas, or on a CMS image field. Brandiseer does not publish the Framer site. - HTML: https://blog.brandiseer.com/use-cases/framer-site-visuals - Markdown: https://blog.brandiseer.com/use-cases/framer-site-visuals/agent.md - JSON: https://blog.brandiseer.com/use-cases/framer-site-visuals/guide.json ### HubSpot campaign creatives - Outcome: An agent generates on-brand email headers, landing-page heroes, ad stills, and campaign thumbnails with Brandiseer; a person then places those image URLs in HubSpot. - HTML: https://blog.brandiseer.com/use-cases/hubspot-campaign-creatives - Markdown: https://blog.brandiseer.com/use-cases/hubspot-campaign-creatives/agent.md - JSON: https://blog.brandiseer.com/use-cases/hubspot-campaign-creatives/guide.json ### Klaviyo email heroes - Outcome: An agent generates on-brand email hero, header, and promo stills with Brandiseer; a person places imageUrl in a Klaviyo template image block or the image library. Brandiseer does not push into Klaviyo and does not send campaigns. - HTML: https://blog.brandiseer.com/use-cases/klaviyo-email-heroes - Markdown: https://blog.brandiseer.com/use-cases/klaviyo-email-heroes/agent.md - JSON: https://blog.brandiseer.com/use-cases/klaviyo-email-heroes/guide.json ### Shopify product visuals - Outcome: An agent generates on-brand PDP heroes, lifestyle stills, collection cards, and promo tiles with Brandiseer; a person places imageUrl in Shopify Files, product media, or theme sections. Brandiseer does not push into Shopify Admin and does not publish the storefront. - HTML: https://blog.brandiseer.com/use-cases/shopify-product-visuals - Markdown: https://blog.brandiseer.com/use-cases/shopify-product-visuals/agent.md - JSON: https://blog.brandiseer.com/use-cases/shopify-product-visuals/guide.json ### Slack creative desk - Outcome: Marketing and ops request on-brand creatives in Slack; the agent pulls Brandiseer brand memory and returns stills in-thread in minutes. - HTML: https://blog.brandiseer.com/use-cases/slack-creative-desk - Markdown: https://blog.brandiseer.com/use-cases/slack-creative-desk/agent.md - JSON: https://blog.brandiseer.com/use-cases/slack-creative-desk/guide.json ### Social media automation - Outcome: On-brand images, platform-native captions, and Buffer scheduling on a recurring cadence in about 20 minutes. - HTML: https://blog.brandiseer.com/use-cases/social-media-automation - Markdown: https://blog.brandiseer.com/use-cases/social-media-automation/agent.md - JSON: https://blog.brandiseer.com/use-cases/social-media-automation/guide.json ### Webflow site visuals - Outcome: An agent generates on-brand Webflow heroes, section stills, and CMS images with Brandiseer; a person or the agent then places those image URLs in Webflow Assets or CMS image fields. - HTML: https://blog.brandiseer.com/use-cases/webflow-site-visuals - Markdown: https://blog.brandiseer.com/use-cases/webflow-site-visuals/agent.md - JSON: https://blog.brandiseer.com/use-cases/webflow-site-visuals/guide.json ### WordPress site visuals - Outcome: An agent generates on-brand heroes, section stills, featured images, and OG cards with Brandiseer; a person places imageUrl in the WordPress Media Library, block editor, featured image, or an existing custom field. Brandiseer does not push into WordPress and does not publish the site. - HTML: https://blog.brandiseer.com/use-cases/wordpress-site-visuals - Markdown: https://blog.brandiseer.com/use-cases/wordpress-site-visuals/agent.md - JSON: https://blog.brandiseer.com/use-cases/wordpress-site-visuals/guide.json ### Ad creative refresh - Outcome: When paid social or display ads go stale (ad fatigue: frequency up, CTR down), an agent briefs and generates fresh on-brand ad image variants with Brandiseer for each placement (square feed, vertical story/reel, landscape display, seasonal or offer variant); a person then downloads imageUrl and uploads it in Meta Ads Manager or Google Ads, or an agent with the advertiser's own API credentials uploads the image into the ad account's image library. Brandiseer does not create, edit, launch, or pause ads or campaigns, does not read ad performance, and does not sync. - HTML: https://blog.brandiseer.com/use-cases/ad-creative-refresh - Markdown: https://blog.brandiseer.com/use-cases/ad-creative-refresh/agent.md - JSON: https://blog.brandiseer.com/use-cases/ad-creative-refresh/guide.json ### Drive & Slides deck visuals - Outcome: An agent generates on-brand stills with Brandiseer for Google Slides decks and Google Drive files (title slide heroes, section dividers, product or feature slide stills, chart or agenda thumbs); a person then downloads imageUrl and inserts into Slides or uploads to Drive, or an agent with Google OAuth / service account credentials uploads to Drive and/or places the image in Slides via presentations.batchUpdate createImage. Brandiseer does not create Drive files or Slides presentations and does not sync. - HTML: https://blog.brandiseer.com/use-cases/drive-slides-deck-visuals - Markdown: https://blog.brandiseer.com/use-cases/drive-slides-deck-visuals/agent.md - JSON: https://blog.brandiseer.com/use-cases/drive-slides-deck-visuals/guide.json ### Linear issue visuals - Outcome: An agent generates on-brand stills with Brandiseer for Linear issues and projects (issue covers, project banners, cycle or roadmap stills, changelog or launch stills); a person then attaches those files in the Linear UI, or an agent with a Linear API key places the public imageUrl into issue or project markdown (or uploads bytes via Linear fileUpload). Brandiseer does not create Linear issues or projects and does not sync. - HTML: https://blog.brandiseer.com/use-cases/linear-issue-visuals - Markdown: https://blog.brandiseer.com/use-cases/linear-issue-visuals/agent.md - JSON: https://blog.brandiseer.com/use-cases/linear-issue-visuals/guide.json ### Notion content visuals - Outcome: An agent queries a Notion content calendar or campaign brief for rows whose Status is Needs visuals, generates an on-brand cover and per-channel creatives with Brandiseer, writes the cover on the page, embeds the creatives, and writes asset links and status back to the row. A person, or a scheduled agent run, asks for that pass. Brandiseer does not watch Notion, and a Notion automation does not call the agent in this guide. - HTML: https://blog.brandiseer.com/use-cases/notion-content-visuals - Markdown: https://blog.brandiseer.com/use-cases/notion-content-visuals/agent.md - JSON: https://blog.brandiseer.com/use-cases/notion-content-visuals/guide.json Use the JSON representation for structured workflow fields and the Markdown representation for the complete source guide.