Overview
Connect LinkedIn with Flows360
Connect and network with professionals
Use the LinkedIn 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 3 actions and no declared triggers.
Available actions
- Create Share Update
- Create Company Update
- Custom API Call
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: LinkedIn
- Package:
@activepieces/piece-linkedin@0.3.0 - Exact artifact digest:
sha256:08eb7e683e829d1a388e80fbf8e8b12b6cc8c5d1f490ee365f0c7d2b52f42475 - Runtime: Activepieces-compatible deterministic worker
- Source: the exact reviewed Activepieces source
Authentication
OAUTH2. 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 Share Update (
create_share_update), Create a share update on LinkedIn Classification: read. - Create Company Update (
create_company_update), Create a new company update for Company Page 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: OAuth 2.0
Required scopes
w_member_socialw_organization_socialrw_organization_adminopenidemailprofile Authentication profiles
connection · oauth2
OAuth scopes: w_member_social, w_organization_social, rw_organization_admin, openid, email, profile
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Create Share Update | Yes | No | Create a share update on LinkedIn |
| Create Company Update | Yes | No | Create a new company update for Company Page |
| Custom API Call | Yes | No | Make a custom API call to a specific endpoint |
Supported actions
Create Share Update · Read
Create a share update on LinkedIn
create_share_update · Risk: low · Retry: safe
Inputs
text· string · Requiredvisibility· string · RequiredimageUrl· object · Optionallink· string · OptionallinkTitle· string · OptionallinkDescription· string · Optional
Create Company Update · Read
Create a new company update for Company Page
create_company_update · Risk: low · Retry: safe
Inputs
company· string · RequiredimageUrl· object · Optionaltext· string · Requiredlink· string · OptionallinkTitle· string · OptionallinkDescription· string · Optional
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 LinkedIn 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.
OAuth scopes
w_member_socialw_organization_socialrw_organization_adminopenidemailprofile
- 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-linkedin@0.3.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 3 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 LinkedIn 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-linkedin@0.3.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.