Repository navigation
docs(readme): Show the live Zapier version and the n8n package on npm - #41
Merged
Merged
Conversation
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues were identified in the documentation-only README update.
No open issues 🎉
What changed in this PR
Updates the README status table to reflect the published Zapier version and n8n package availability on npm.
Changes:
- Updates Zapier to version 1.3.0 with all documented triggers, actions, and searches.
- Replaces the outdated n8n unpublished status with npm availability, provenance, installation, and verification details.
- Makes documentation-only changes with no code, dependency, or workflow updates.
| File | Description |
|---|---|
| README.md | Updates the Zapier and n8n entries in the platform status table. |
Review effort: Lite
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was wrong
Two rows of the Status table in
README.mdno longer match what users get.TaskadeCLIAPI@1.3.0for each of them (for examplenew_comment,run_agent,find_agent,custom_api_call), andpackage.jsonis at1.3.0.n8n-nodes-taskade1.0.0 and 1.0.1 are on npm since 2026-11-18 (fix(n8n): Publish the package with public access #38, chore(n8n): Release 1.0.1 through npm trusted publishing #39). Version 1.0.1 came frompublish-n8n.ymlwith an npm provenance statement.What the README says now
No other line changes. No code, dependency or workflow change.
How I checked
curl -sL https://zapier.com/apps/taskade/integrations, then I decoded theAppImplementationActionIDs in the page data: 40 IDs, allTaskadeCLIAPI@1.3.0, which cover the 6 triggers, 22 actions, 4 searches and 8 hidden helpers insrc/index.ts.npm view n8n-nodes-taskade versions dist-tagsgives1.0.1aslatest.npm view n8n-nodes-taskade@1.0.1 dist.attestationsshows an SLSA provenance statement.curl -s -o /dev/null -w '%{http_code}' -L.yarn install --frozen-lockfileandyarn lintpass locally.How to check
npm view n8n-nodes-taskade dist-tags.