Repository navigation
v0.2.0: broad coverage, triggers, batch actions, API request - #1
Merged
Merged
Conversation
added 3 commits
October 28, 2026 15:42
… and phone checks)
…ions, polling and instant trigger nodes, logo
…k dedupe, README cleanup; MIT notice
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.
Summary
Adds: BatchData node covering V1-V3 operations (reverse skip trace, permits, batch skip trace, batch lookup, batch address verify, autocomplete, geocode, reverse geocode, investor buy box and properties, search sessions, property monitors, generic API request); BatchData Trigger (polling: new search session, new monitor, new session property); BatchData Monitor Trigger (webhook: create/check/delete subscription, eventId dedupe, optional billed hydration).
Testing: 37 node:test tests pass;
n8n-node lint, build and tsc clean.Risk: Medium. New customer-facing integrations; no production services touched. Billing is per record, so a bug that sends extra requests costs customers money. Property monitors are limited (5 per team, immutable), so a bug in subscribe/unsubscribe could use up a team's slots.
How to revert: Do not publish. If already published, unpublish or deprecate the package/app version and revert this PR.
Required reviewers: One engineer for code. Ivo for naming and the phone-compliance and billing wording.
Review: Post-coding review by Claude, see
review/claude-review-v02.md(or the note in the final report if it could not run); plus a self-review.Webhook decision: Instant triggers create a V2 property subscription with
deliveryConfig {type: "webhook", url: <the trigger's own hook URL>}on subscribe and delete it on unsubscribe. Users never enter a callback URL;webhookUrlanderrorWebhookUrlare stripped or blocked everywhere else.Billed hydration (opt-in): The instant trigger delivers IDs only. Adding the full property record runs a billed property lookup per event, so it is off by default (a toggle in n8n and Zapier, a separate module in Make).
Verified vs mocked: Everything except monitors and the instant triggers was checked live with 1 record per call. Monitors and instant triggers are mocked only (the available token gets 403 on subscription endpoints); verify with a sandbox token before publishing.
Review result: Claude post-coding review ran on the v0.2.0 code. Findings fixed in this PR: callback keys now stripped from free-form query JSON (n8n, Zapier); Make API call blocks (and sends no body or query for) bodies that contain
webhookor a JSON unicode escape, and the Make instant trigger dedupes oneventId; stale Zapier README bullets removed. Known gap, documented: Make cannot strip callback keys recursively in the Additional Criteria JSON fields (synchronous endpoints ignore them).