Overview
Connect Writesonic with Flows360
Writesonic AI-powered writing assistant
Use the Writesonic 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 11 actions and no declared triggers.
Available actions
- Blog Ideas
- Blog Intros
- Blog Outlines
- Content Rephraser
- Content Shorten
- Facebook Ads
- Generate Product Descriptions
- Google Ads
- Plus 3 additional declared actions.
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: Writesonic
- Package:
@activepieces/piece-writesonic-bulk@0.2.0 - Exact artifact digest:
sha256:4a699ff31b6787382d1d775fb5b7f0914b0ab7af1064392308264befdd20178b - 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
- Blog Ideas (
blogIdeas), Generate blog article ideas based on a topic or keyword Classification: read. - Blog Intros (
blogIntros), Generate enticing blog article introductions Classification: read. - Blog Outlines (
blogOutlines), Generate detailed article outlines for better content writing Classification: read. - Content Rephraser (
contentRephraser), Rephrase content in a different voice and style to appeal to different readers Classification: read. - Content Shorten (
contentShorten), Shorten your content in a different voice and style to appeal to different readers Classification: read. - Facebook Ads (
facebookAds), Generate Facebook ad copies that make your ads truly stand out Classification: read. - Generate Product Descriptions (
generateProductDescriptions), Generate authentic product descriptions that compel, inspire, and influence Classification: read. - Google Ads (
googleAds), Generate quality ads that rank in search results and drive more traffic Classification: read. - Landing Page Headlines (
landingPageHeadlines), Generate unique and catchy headlines perfect for your product or service Classification: read. - Sentence Expander (
sentenceExpander), Expand short sentences into more descriptive and interesting ones Classification: read. - Custom API Call (
custom_api_call), Make a custom API call to a specific endpoint Classification: read.
Trigger contracts
- No trigger delivery contracts are declared.
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
- Writesonic Bulk API Key Required · protected credential
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Blog Ideas | Yes | No | Generate blog article ideas based on a topic or keyword |
| Blog Intros | Yes | No | Generate enticing blog article introductions |
| Blog Outlines | Yes | No | Generate detailed article outlines for better content writing |
| Content Rephraser | Yes | No | Rephrase content in a different voice and style to appeal to different readers |
| Content Shorten | Yes | No | Shorten your content in a different voice and style to appeal to different readers |
| Facebook Ads | Yes | No | Generate Facebook ad copies that make your ads truly stand out |
| Generate Product Descriptions | Yes | No | Generate authentic product descriptions that compel, inspire, and influence |
| Google Ads | Yes | No | Generate quality ads that rank in search results and drive more traffic |
| Landing Page Headlines | Yes | No | Generate unique and catchy headlines perfect for your product or service |
| Sentence Expander | Yes | No | Expand short sentences into more descriptive and interesting ones |
| Custom API Call | Yes | No | Make a custom API call to a specific endpoint |
Setup
Setup
- Add the Writesonic 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-writesonic-bulk@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 11 actions 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.
- 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 Writesonic 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-writesonic-bulk@0.2.0 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.