01
Truthful starting point
DewEngine has no LinkedIn node for n8n
There is no released DewEngine n8n package or LinkedIn connector. Profiles, search, messages, invitations, posts, and other catalog entries are decision-gated targets only. A workflow editor should not display executable LinkedIn operations until legal and provider authorization, connector conformance, and the n8n adapter all pass. This guide is an architecture checklist, not setup instructions.
- Keep gated nodes out of production credentials and menus
- Label fake workflow tests so they cannot be mistaken for provider traffic
02
Credential model
Authenticate n8n to the customer application boundary
A workflow credential should be scoped to one DewEngine workspace and environment, revocable, rotated, and limited to the needed read or action classes. It must not contain LinkedIn session material. The acting professional account remains an opaque resource chosen under customer role checks. Exported workflow JSON must never carry secrets or another customer's account identifiers.
- Use separate credentials for test and production
- Redact secrets and personal fields from execution data
03
Trigger design
Distinguish provider observations from scheduled checks
A future webhook trigger requires an approved LinkedIn observation, stable event ID, account scope, deduplication, signed delivery, retry, and replay behavior. A Cron node that reads a CRM table is not a real-time LinkedIn trigger. Workflows should store the last accepted event and make downstream writes idempotent because n8n can replay or resume executions after failure.
- Verify signatures before processing event content
- Keep polling cursors bound to account and query scope
04
Approval flow
Use n8n to coordinate review, not erase it
The workflow can gather authorized context, prepare a draft, create a CRM task, and wait for a human decision. Sensitive LinkedIn actions would require final sender, recipient, content, purpose, suppression, account health, entitlement, and budget checks at execution. Approval expires after material changes. A generic continue node must not turn a proposal into standing permission for future recipients.
- Persist the approval outside transient workflow memory
- Require new approval after content or destination changes
05
Error branches
Route unknown outcomes away from automatic retry
Input, authentication, policy-gated, account-action-required, throttled, transient pre-dispatch, provider rejection, and indeterminate failures need different branches. Only definitely safe transient work may retry with bounds. If a provider-visible attempt could have occurred, keep the durable command indeterminate and reconcile through an approved read path. Switching accounts or adding random delays to escape a refusal is prohibited.
- Make the error type drive the branch
- Notify an accountable owner when user action is required
06
Release proof
Test workflow replay and connector stop together
Qualification needs scoped credential tests, tenant substitution, webhook replay, duplicate executions, approval expiry, timeout ambiguity, throttling, account restriction, kill switch, secret rotation, workflow export, personal-data retention, and deletion. LinkedIn additionally requires counsel, provider authorization, eligible-product fixtures, and consented conformance. Until then, n8n workflows should stay on internal CRM and review tasks only.
- Replay completed executions without repeating external action
- Prove revoked credentials and accounts halt queued nodes