Overview
Connect IBM Cognos Analytics with Flows360
Business intelligence and performance management suite for data analysis and reporting
Use the IBM Cognos Analytics 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 9 actions and no declared triggers.
Available actions
- Create Data Source
- Get Data Source
- Update Data Source
- Delete Data Source
- Get Content Object
- Update Content Object
- Move Content Object
- Copy Content Object
- Plus 1 additional declared action.
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: IBM Cognos Analytics
- Package:
@activepieces/piece-ibm-cognose@0.2.0 - Exact artifact digest:
sha256:43ddc495796c2b93b11e1305da0062d8d23ce19b149655da66dca55f013c6930 - Runtime: Activepieces-compatible deterministic worker
- Source: the exact reviewed Activepieces source
Authentication
CUSTOM AUTH. 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 Data Source (
create_data_source), Create a new data source Classification: read. - Get Data Source (
get_data_source), Retrieve data source details Classification: read. - Update Data Source (
update_data_source), Update an existing data source Classification: read. - Delete Data Source (
delete_data_source), Delete a data source Classification: read. - Get Content Object (
get_content_object), Get content object details Classification: read. - Update Content Object (
update_content_object), Update an existing content object Classification: read. - Move Content Object (
move_content_object), Move an object with all its descendants Classification: read. - Copy Content Object (
copy_content_object), Copy an object optionally with all its descendants 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
- Base URL Required
- CAM Namespace Required
- Username Required
- Password Required · protected credential
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Create Data Source | Yes | No | Create a new data source |
| Get Data Source | Yes | No | Retrieve data source details |
| Update Data Source | Yes | No | Update an existing data source |
| Delete Data Source | Yes | No | Delete a data source |
| Get Content Object | Yes | No | Get content object details |
| Update Content Object | Yes | No | Update an existing content object |
| Move Content Object | Yes | No | Move an object with all its descendants |
| Copy Content Object | Yes | No | Copy an object optionally with all its descendants |
| Custom API Call | Yes | No | Make a custom API call to a specific endpoint |
Supported actions
Create Data Source · Read
Create a new data source
create_data_source · Risk: low · Retry: safe
Inputs
defaultName· string · Required, Name for the new data sourceconnectionString· string · Required, JDBC URL or database connection stringdriverName· string · Optional, Database driver class nameusername· string · Optional, Username for database connectionpassword· string · Optional, Password for database connectionsignonDefaultName· string · Optional, Name for the database credentials
Get Data Source · Read
Retrieve data source details
get_data_source · Risk: low · Retry: safe
Inputs
datasourceId· string · Required, Select a data sourcefields· string · Optional, Comma-separated list of extra fields (e.g., connections,signons)
Update Data Source · Read
Update an existing data source
update_data_source · Risk: low · Retry: safe
Inputs
datasourceId· string · Required, Select a data sourcedefaultName· string · Optional, New name for the data sourcedisabled· boolean · Optional, Disable the data sourcehidden· boolean · Optional, Hide the data source
Delete Data Source · Read
Delete a data source
delete_data_source · Risk: low · Retry: safe
Inputs
datasourceId· string · Required, Select a data source
Get Content Object · Read
Get content object details
get_content_object · Risk: low · Retry: safe
Inputs
objectId· string · Required, Select a content objectfields· string · Optional, Comma-separated list of extra fields (e.g., owner,permissions,children)
Update Content Object · Read
Update an existing content object
update_content_object · Risk: low · Retry: safe
Inputs
objectId· string · Required, Select a content objecttype· string · Required, Object type (e.g., report, dashboard, folder)defaultName· string · Optional, New name for the objectdefaultDescriptions· string · Optional, New description for the objectversion· number · Optional, Current version for optimistic concurrency
Move Content Object · Read
Move an object with all its descendants
move_content_object · Risk: low · Retry: safe
Inputs
sourceId· string · Required, Select a content objectdestinationId· string · Required, Destination container where the object will be moved
Copy Content Object · Read
Copy an object optionally with all its descendants
copy_content_object · Risk: low · Retry: safe
Inputs
sourceId· string · Required, Select a content objectdestinationId· string · Required, Destination container where the object will be copiedrecursive· boolean · Optional, Copy all descendants (child objects)
Custom API Call · Read
Make a custom API call to a specific endpoint
custom_api_call · Risk: low · Retry: safe
Inputs
url· object · Requiredmethod· string · Requiredheaders· object · Optional, Authorization headers are injected automatically from your connection.queryParams· object · Optional, Appended to the URL as ?key=value.body_type· string · Optionalbody· object · Optionalresponse_is_binary· boolean · Optional, Enable for files like PDFs, images, etc.failsafe· boolean · Optional, On a failed request, output the error instead of failing the step.timeout· number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).followRedirects· boolean · Optional, Follow 3xx redirects instead of returning them as the response.
Setup
Setup
- Add the IBM Cognos Analytics 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:
- Base URL (
baseurl), required. - CAM Namespace (
CAMNamespace), required. - Username (
username), required. - Password (
password), required; stored as a sensitive connection value.
- 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-ibm-cognose@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 9 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 IBM Cognos Analytics 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-ibm-cognose@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.