1. Choose Solo or Team and enter your company and team names separately.
2. Define your LinkedIn audience, topics, writing style, posting cadence, and approver.
3. Review the Content Engine and export the generated posting plan or prompt from TALOS.
4. Keep your TALOS exports available for mapping into Make.

TALOS's HTML interface does not by itself create a live Make connection or securely store third-party API keys.

1. Sign in to Make and select Create a new scenario.
2. If you have a TALOS-compatible Make blueprint JSON, open the scenario editor's menu and choose Import blueprint; select the JSON file. Otherwise build the modules manually.
3. Inspect every imported module. Re-select connections and repair any missing configuration or mappings.
4. Save the scenario with a recognizable name, such as TALOS · Content Review & Publishing.

Make: scenario blueprints and connections ↗

1. Simple starting path: use a Google Sheet or another supported source containing exported TALOS post records. Configure a Make trigger such as Watch New Rows.
2. Advanced path: add Webhooks → Custom webhook in Make, then create the webhook URL. A secure TALOS server-side integration would be required to send records automatically; a static HTML page alone is not a secure webhook connector.
3. Map fields such as post_id, post_text, scheduled_at, approval_status, and linkedin_profile where available.

Make: custom webhooks ↗

1. Add a supported AI app/module in Make or use its HTTP module for an officially supported API.
2. Create the provider connection in Make and store credentials in Make's secure connection/keychain features, not in TALOS HTML, exported JSON, or browser storage.
3. Map TALOS's content instructions and verified facts into the request, and capture the generated post text in a downstream field.
4. Test with a non-sensitive sample. Verify the output matches the desired voice and does not invent hiring claims.

Make: HTTP module and secure credentials ↗

1. Route generated drafts to an approval step (for example, a review table or an approval-capable application).
2. Require an explicit Approved status before any publishing action can execute.
3. Use filters to prevent rejected, unreviewed, duplicate, or previously published records from reaching a publisher.
4. Record reviewer, decision, timestamp, and final approved text for auditability.

Do not enable automatic posting until the review gate is tested and functioning.

1. In Make, look for a supported LinkedIn integration or approved publishing provider with the permissions required for your account type.
2. Authorize the relevant LinkedIn account through the provider's supported connection flow.
3. Map the approved post body and target profile/page. Check permissions: posting to a personal profile is not the same as posting to a company page.
4. If the desired publishing action is unavailable, use a manual publishing handoff rather than trying to bypass LinkedIn access restrictions.

LinkedIn publishing permissions and available modules vary by app, account and authorization. TALOS cannot guarantee direct personal-profile publishing.

1. Use a clearly labeled test record and click Run once in Make.
2. Confirm field mapping, AI output, approval routing, duplicate prevention, and the intended publishing destination.
3. Start with a manual approval and a single post; inspect scenario history for errors.
4. Choose an appropriate schedule (or an instant webhook trigger), save, then activate the scenario when ready.
5. Monitor executions, API usage, posting status and failure alerts.

Make: activation guide ↗

1. Nothing triggers: check whether the scenario is active, whether its schedule is enabled, and whether new records match the trigger.
2. Blank post fields: run once and inspect module outputs, then correct the mapped field names.
3. Authorization fails: reconnect the affected service inside Make and confirm its account permissions.
4. Duplicate posts: verify unique post IDs and a published-status check before publishing.
5. Publishing blocked: confirm the LinkedIn connection and permitted publishing target; use manual handoff if unsupported.