Skip to content
← Back to documentation
Technical Reference

JoggAI

AI-powered content creation platform for generating avatar photos, videos, and product content using advanced AI technology.

CategoryArtificial Intelligence
Authenticationcustom
Version0.1.6
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect JoggAI with Flows360

AI-powered content creation platform for generating avatar photos, videos, and product content using advanced AI technology.

Use the JoggAI 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 8 actions and 2 triggers.

Available actions

  • Create AI Avatar Photo
  • Create Avatar Video
  • Create Product from URL
  • Create Product from Product Info
  • Update Product Info
  • Get Generated Video
  • Upload Media
  • Create Video from Template

Available triggers

  • Video Generated Successfully
  • Video Generation Failed

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: JoggAI
  • Package: @activepieces/piece-jogg-ai@0.1.6
  • Exact artifact digest: sha256:43c080fa4f6a2d924b829ca6a3a93b8791bbf33a0863bef229989f10358d6269
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

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

Action contracts

  • Create AI Avatar Photo (createAiAvatarPhoto), Creates an AI avatar photo using JoggAI API Classification: read.
  • Create Avatar Video (createAvatarVideo), Creates an avatar video using JoggAI API Classification: read.
  • Create Product from URL (createProductFromUrl), Creates a product by crawling product information from a URL Classification: read.
  • Create Product from Product Info (createProductFromProductInfo), Creates a product from product information Classification: read.
  • Update Product Info (updateProductInfo), Updates existing product information using product ID Classification: read.
  • Get Generated Video (getGeneratedVideo), Get information about a specific generated video project using its ID Classification: read.
  • Upload Media (uploadMedia), Generate a signed URL for file upload. Use the returned sign_url to upload your file with a PUT request. Classification: read.
  • Create Video from Template (createVideoFromTemplate), Creates a new video from templates Classification: read.

Trigger contracts

  • Video Generated Successfully, webhook.
  • Video Generation Failed, webhook.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects10
Supported actionsNot published
Triggers2

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create AI Avatar Photo Yes No Creates an AI avatar photo using JoggAI API
Create Avatar Video Yes No Creates an avatar video using JoggAI API
Create Product from URL Yes No Creates a product by crawling product information from a URL
Create Product from Product Info Yes No Creates a product from product information
Update Product Info Yes No Updates existing product information using product ID
Get Generated Video Yes No Get information about a specific generated video project using its ID
Upload Media Yes No Generate a signed URL for file upload. Use the returned sign_url to upload your file with a PUT request.
Create Video from Template Yes No Creates a new video from templates
Video Generated Successfully Yes No webhook trigger declared by the pinned package.
Video Generation Failed Yes No webhook trigger declared by the pinned package.

Triggers

Video Generated Successfully · Webhook

Fires when a video is generated successfully

Video Generation Failed · Webhook

Fires when video generation fails

Setup

Setup

  1. Add the JoggAI 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-jogg-ai@0.1.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 8 actions and 2 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 JoggAI 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-jogg-ai@0.1.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.