LinkedIn integration

What it does

The LinkedIn integration lets your agency publish content to a client's personal profile or company page, watch a company page for new shares, and pull profile and organization metadata without leaving TaskJuice. Connect a client's LinkedIn account once and you can list the organization pages the member can administer, fetch a single organization, publish a UGC post on behalf of the member or a page, delete a previously published post, and fire a workflow whenever a watched page publishes a new share.

Connect a LinkedIn account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose LinkedIn and click Connect.
3. Sign in with the LinkedIn account that owns or administers the pages you want to manage on behalf of your client.
4. Grant the requested scopes (openid, profile, email, w_member_social, r_organization_social, w_organization_social, rw_organization_admin).
5. TaskJuice returns you to the workspace with the connection ready to use in any workflow.

To revoke access at any time, open LinkedIn permitted services and remove the TaskJuice entry.

Triggers

• linkedin/new-organization-share polls a chosen organization page's share list and fires once per cycle whose items array carries every new share observed since the previous watermark. Drop a Loop node downstream to process each share individually.

Actions

• linkedin/get-userinfo fetches the OpenID Connect profile for the connected LinkedIn member, including the member URN and verified email.
• linkedin/list-organization-acls lists the organization pages the connected member can administer, filtered by role and ACL state, paginated by start and count.
• linkedin/get-organization fetches a single organization page by id and returns the vanity name, localized name, website, and description.
• linkedin/create-ugc-post publishes a text UGC post as a member or organization, with configurable visibility (PUBLIC, CONNECTIONS, LOGGED_IN, CONTAINER).
• linkedin/delete-ugc-post deletes a UGC post by URN. The connected token must have authored the post.

Known limitations

• LinkedIn offers two real-time delivery surfaces: Lead Sync webhooks (for lead-gen form submissions) and the social-actions event stream (for member and organization activity). Both carry payload shapes incompatible with the current TaskJuice inbound-auth envelope, which supports HMAC variants only. The Lead Sync subscription lifecycle also requires per-organization webhook registration through a separate REST endpoint, which is outside the declarative envelope's auto-provisioning model. Until those land as declarative recipes, the LinkedIn integration uses the linkedin/new-organization-share polling trigger with a default 15 minute interval to stay comfortably under the daily call quota.
• LinkedIn enforces application-level daily call quotas and per-endpoint throttles, signaled with a 429 status and a Retry-After header. TaskJuice surfaces a 429 as a retryable rate-limit error and respects the documented backoff.
• The linkedin/create-ugc-post action currently supports text-only shares (shareMediaCategory: NONE). Media-attached shares require a two-step registerUpload plus ugcPosts flow that is not yet available in the declarative envelope.
• Publishing as an organization page requires the connected member to hold the ADMINISTRATOR or DIRECT_SPONSORED_CONTENT_POSTER role on that page. Use linkedin/list-organization-acls to discover the URNs of pages the connected token can post as.
• The openid, profile, and email scopes are required for linkedin/get-userinfo. The rw_organization_admin scope is required for linkedin/list-organization-acls. Without them, both surface a 403 from LinkedIn on the first request.