n8n-nodes-postial 0.2.0 → 0.2.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +7 -5
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
|
-
# Postial
|
|
1
|
+
# Postial for n8n
|
|
2
2
|
|
|
3
|
-
Community nodes for [Postial](https://postial.co), by productivity-boost.com Betriebs UG. Create social posts and receive publishing and approval events in n8n.
|
|
3
|
+
Community nodes for [Postial](https://postial.co), formerly published as SocialMint, by productivity-boost.com Betriebs UG. Create social posts and receive publishing and approval events in n8n.
|
|
4
4
|
|
|
5
|
-
Version 0.2.
|
|
5
|
+
Version 0.2.1. MIT licensed. Install the renamed package `n8n-nodes-postial`.
|
|
6
6
|
|
|
7
7
|
## Installation
|
|
8
8
|
|
|
@@ -55,6 +55,8 @@ API error messages appear in node errors. Use n8n's **On Error → Continue (usi
|
|
|
55
55
|
|
|
56
56
|
Example: Schedule Trigger → Postial (Post / Create). Select the brand and channels, enter `Weekly update`, choose Scheduled Time, and set a future date. Enable Requires Approval when review is needed.
|
|
57
57
|
|
|
58
|
+
After importing `examples/create-scheduled-post.json`, assign a Postial API credential to its Postial node before running the workflow.
|
|
59
|
+
|
|
58
60
|
The execution method uses n8n's authenticated HTTP helper for all network requests. Programmatic execution keeps pagination, input pairing, and per-item idempotency consistent across operations; credential authentication and testing use n8n's declarative definitions. There are no external runtime dependencies or runtime file/environment access.
|
|
59
61
|
|
|
60
62
|
## Postial Trigger
|
|
@@ -71,7 +73,7 @@ Delivery is at least once: deduplicate using the event `id` when downstream acti
|
|
|
71
73
|
|
|
72
74
|
The automatic signing secret is in workflow static data; the manual secret is a password-masked node parameter. These are not n8n encrypted credentials. Restrict workflow/database/export access and remove secrets and static data before sharing exports.
|
|
73
75
|
|
|
74
|
-
Import [examples/approval-to-slack.json](examples/approval-to-slack.json),
|
|
76
|
+
Import [examples/approval-to-slack.json](examples/approval-to-slack.json), assign a Postial API credential to its Postial Trigger and a Slack credential to its Slack node, replace the Slack channel ID, then activate it. It sends the approval decision and post link to Slack. To send email instead, replace the Slack node with n8n's Send Email node and use `$json.data.decision` and `$json.data.post_url`.
|
|
75
77
|
|
|
76
78
|
## Validation
|
|
77
79
|
|
|
@@ -106,7 +108,7 @@ Production deliberately rejects loopback webhook destinations. The smoke runner
|
|
|
106
108
|
|
|
107
109
|
## Release
|
|
108
110
|
|
|
109
|
-
Trusted Publishing is configured for this repository. After checks, push the matching version tag (`git tag
|
|
111
|
+
Trusted Publishing is configured for this repository. After checks, push the matching version tag (`git tag v$(node -p "require('./package.json').version")` followed by `git push origin v$(node -p "require('./package.json').version")`). The Publish GitHub Action runs `npm ci`, lint, build, and tests, then `npm publish --provenance --access public` using GitHub OIDC. Tags must match the package version. Do not publish from a local shell.
|
|
110
112
|
|
|
111
113
|
Before tagging, run all validation commands and the local smoke test, inspect `npm pack --dry-run`, and perform an n8n editor activation/deactivation test. After publication, verify npm provenance, run `npx @n8n/scan-community-package n8n-nodes-postial`, and submit for n8n verification.
|
|
112
114
|
|
package/package.json
CHANGED