Overview
Connect FeedHive with Flows360
Schedule, manage and publish social media content with FeedHive.
Use the FeedHive 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 Post
- Update Post
- Get Post
- Delete Post
- List Posts
- Create Label
- Create Post via Trigger
- Custom API Call
Available triggers
- Post Notification
- Comment Notification
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: FeedHive
- Package:
@activepieces/piece-feedhive@0.1.0 - Exact artifact digest:
sha256:4194e90e560aede5c57916a2175d7e90c064cb234efeb371b3f2c0d6514e1a04 - 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 Post (
create_post), Creates a new post in FeedHive (draft or scheduled). Classification: read. - Update Post (
update_post), Updates an existing post in FeedHive. Only the fields you fill in will be changed. Classification: read. - Get Post (
get_post), Retrieves the details of a specific post. Classification: read. - Delete Post (
delete_post), Deletes a post from FeedHive. This action cannot be undone. Classification: read. - List Posts (
list_posts), Returns a list of posts, optionally filtered by status or labels. Classification: read. - Create Label (
create_label), Creates a new label in FeedHive for organising posts. Classification: read. - Create Post via Trigger (
fire_workflow_trigger), Fires a FeedHive Workflow Trigger to create a post. The workflow defines which accounts to post to, the AI model to use, and any default content. Classification: read. - Custom API Call (
custom_api_call), Make a custom API call to a specific endpoint Classification: read.
Trigger contracts
- Post Notification, webhook.
- Comment Notification, 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 Post | Yes | No | Creates a new post in FeedHive (draft or scheduled). |
| Update Post | Yes | No | Updates an existing post in FeedHive. Only the fields you fill in will be changed. |
| Get Post | Yes | No | Retrieves the details of a specific post. |
| Delete Post | Yes | No | Deletes a post from FeedHive. This action cannot be undone. |
| List Posts | Yes | No | Returns a list of posts, optionally filtered by status or labels. |
| Create Label | Yes | No | Creates a new label in FeedHive for organising posts. |
| Create Post via Trigger | Yes | No | Fires a FeedHive Workflow Trigger to create a post. The workflow defines which accounts to post to, the AI model to use, and any default content. |
| Custom API Call | Yes | No | Make a custom API call to a specific endpoint |
| Post Notification | Yes | No | webhook trigger declared by the pinned package. |
| Comment Notification | Yes | No | webhook trigger declared by the pinned package. |
Triggers
Post Notification · Webhook
Triggers when a post is published, scheduled, or fails.
Inputs
event_type· stringinstructions· string
Comment Notification · Webhook
Triggers when a comment is added to one of your posts.
Inputs
instructions· string
Setup
Setup
- Add the FeedHive 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-feedhive@0.1.0; 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.
- 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 FeedHive 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-feedhive@0.1.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.