Overview
Connect Predis.ai with Flows360
AI-powered social media content creation platform. Generate posts, videos, carousels, images, quotes, and memes with automated creation and webhook notifications.
Use the Predis.ai 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 1 trigger.
Available actions
- Create Content
Available triggers
- Post Created
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: Predis.ai
- Package:
@activepieces/piece-predis-ai@0.0.8 - Exact artifact digest:
sha256:33cfe08dca7c1069e33e9987b5d26473e240a3dc4b8ecd62978d76f73278c810 - 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 Content (
create_content), Generate posts including videos, carousels, images, quotes, and memes. Classification: read.
Trigger contracts
- Post Created, webhook.
Verification
Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.
Capability summary
Authentication
Authentication method: custom
Authentication profiles
connection · custom
- API Key Required · protected credential
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Create Content | Yes | No | Generate posts including videos, carousels, images, quotes, and memes. |
| Post Created | Yes | No | webhook trigger declared by the pinned package. |
Supported actions
Create Content · Read
Generate posts including videos, carousels, images, quotes, and memes.
create_content · Risk: low · Retry: safe
Inputs
brand_id· string · Required, Unique identifier of your brand. Find it in Predis.ai under your brand settings.text· string · Required, The topic for your post. Must be at least 20 characters and 3 words.model_version· string · Optional, Version 4 offers higher quality but only supports single_image and carousel.media_type· string · Optional, Type of media to generate. Video is only supported by model version 2.post_type· string · Optional, Type of post to generate. Only supported by model version 2.n_posts· number · Optional, Number of posts to generate (1-10).input_language· string · Optional, Language of your input text.output_language· string · Optional, Language for the generated post.video_duration· string · Optional, Required when media type is video.color_palette_type· string · Optional, Color palette for generated content.author· string · Optional, Author name. Required when post type is quotes.template_ids· array · Optional, List of template IDs to use. Only supported by model version 2.media_urls· array · Optional, List of image/video URLs to use in your post. Only supported by model version 2.
Triggers
Post Created · Webhook
Triggers when a post generation completes or fails.
Inputs
markdown· string
Setup
Setup
- Add the Predis.ai connector to the workflow in the target Flows360 Studio instance.
- 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.
- Provide the connection fields declared by the pinned package:
- No provider credential fields are declared by the pinned package.
- Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
- Test the workflow in the appropriate environment before enabling production scheduling or event delivery.
Limitations
Limitations and operational notes
- This content describes
@activepieces/piece-predis-ai@0.0.8; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 1 action and 1 trigger 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.
- Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.
Troubleshooting
Why canu2019t the connector authenticate?
Check the tenant connection in Studio and confirm every required Predis.ai 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-predis-ai@0.0.8 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.