This repository was archived by the owner on Aug 13, 2026. It is now read-only.
feat: add Plivo tool nodes and credential - #6714
Open
sarveshpatil-plivo wants to merge 2 commits into
Open
Conversation
sarveshpatil-plivo
force-pushed
the
plivo-nodes
branch
from
August 6, 2026 12:16
d456e1a to
bb351f9
Compare
dblagbro
added a commit
to dblagbro/flow-wiser
that referenced
this pull request
Aug 12, 2026
…ill merging (#18) The 2026-08-05 snapshot was taken because "upstream repository moves to public archive on 2026-08-10, which locks issues and pull requests". That did not happen. Verified 2026-08-12: archived=false, disabled=false, comments still working, and three pull requests merged on 2026-08-07 -- after the documented 2026-07-29 code freeze and after the snapshot was taken. Upstream is frozen, not closed. Contributions can still be commented on and, on this evidence, still merged. This contradicts docs/PROJECT-LOG.md, docs/product.md and docs/STATUS.md, which all assert the archive happened. It also makes a public comment on upstream FlowiseAI#6706 wrong. Both are flagged in DELTA-2026-08-12.md rather than corrected here, because the licensing narrative is REVIEW REQUIRED and belongs to a human. Synced: * 3 new PRs captured as git am-able patches -- FlowiseAI#6714, FlowiseAI#6723, FlowiseAI#6725 * 3 upstream-MERGED fixes this fork does not have, captured to merged-after-snapshot/ -- FlowiseAI#6680, FlowiseAI#6708, FlowiseAI#6709, all maintainer-authored * prs/index.json refreshed 347 -> 346, issues 698 -> 701 * both indexes normalised to a single JSON array; the originals were 11 concatenated per-page arrays that parse only with jq -s. Data was complete in both, only the shape changed. Licence check applied to all six new patches: no diff hunks against packages/server/src/enterprise/ or IdentityManager.ts. All clean, no stripping required, and no hunk content was read to determine it -- decisions made on the diff --git path headers alone, per docs/CLEANROOM-PROTOCOL.md. DELTA-2026-08-12.md also records where Flow-Wiser has already solved a still-open upstream PR, with the fork's fix being the more complete one in every confirmed case: FlowiseAI#6670 and FlowiseAI#6642 (the unpinned Docker version -- this fork's founding defect, still open upstream from two independent reporters), FlowiseAI#6706 (connect-sqlite3), and FlowiseAI#4805 (Node 22, open since 2025-07-06 for the change ADR-0004 completed this week across ten locations rather than three). Contributing any of it back is an outward action and is left for authorization. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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 this PR adds
Two Plivo tool nodes and a credential so an agent can reach the phone network from a Flowise flow.
Both nodes sit under Tools and register automatically through the nodes pool, so no registry file is touched. Each node ships its own icon, and the credential follows the same shape as the other API-key credentials.
How it was tested
Both actions were tested against a live Plivo account. Sending an SMS returns the message UUID and placing a call returns the request UUID. The components package builds cleanly with the nodes present.
Notes
No new dependency is added. Audio streaming is out of scope for a tool node.