Palaccio Zapier Webhook API
MarketingMarketing AutomationapiKey1 EndpointsREST
For Agents
Retrieve recent leads from Palaccio, subscribe to lead webhooks, and unsubscribe from lead notifications via Zapier integration.
Use for: Get recent leads from Palaccio, Subscribe to Palaccio lead webhooks, Unsubscribe from Palaccio webhooks, Retrieve lead contact information
Not supported: Does not capture leads directly, host landing pages, or send emails - use only for retrieving lead data and managing webhook subscriptions. Lead capture happens through Palaccio's web forms and landing pages.
Palaccio Zapier Webhook API provides a single endpoint for managing lead data through Zapier integrations. The API supports retrieving recent leads, subscribing to webhook notifications for new leads, and unsubscribing from webhooks. Authentication uses a zapierKey query parameter that identifies the user account. The API is designed specifically for Zapier workflow automation, enabling real-time lead capture and distribution to CRMs, spreadsheets, and notification systems.
Install Jentic One Beta
Connect the Palaccio Zapier Webhook API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Palaccio Zapier Webhook API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpalaccio.com%2Fpalaccio-zapier-webhook" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpalaccio.com%2Fpalaccio-zapier-webhook" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Palaccio Zapier Webhook API.
Retrieve recent leads with name, email, phone, and metadata
Subscribe to webhook notifications for new leads captured by Palaccio
Unsubscribe from webhook notifications
Authenticate requests using per-user Zapier keys
Use Cases
Patterns agents use Palaccio Zapier Webhook API for, with concrete tasks.
★ CRM Lead Sync via Zapier
Automatically sync leads captured by Palaccio into a CRM like Salesforce, HubSpot, or Pipedrive using Zapier. Subscribe to webhooks with action=subscribeHook and hookUrl pointing to a Zapier webhook trigger. When a new lead is captured, Palaccio sends lead details to the webhook, and Zapier routes them to the CRM, creating contacts and opportunities without manual data entry.
GET /?zapierKey={key}&action=subscribeHook&hookUrl={url} to register the webhook for lead notifications.
Lead Retrieval for Reporting Dashboards
Fetch recent leads captured during a specific time period for analytics dashboards or reporting tools. Call GET /?zapierKey={key}&action=getRecentLeads to retrieve the latest lead data, including name, email, phone, and timestamps. This supports weekly sales reports, lead source attribution, and campaign performance analysis.
GET /?zapierKey={key}&action=getRecentLeads to retrieve the most recent leads.
Webhook Cleanup and Unsubscribe
When a Zapier workflow is deleted or deactivated, unsubscribe from Palaccio lead webhooks to stop receiving notifications. Call GET /?zapierKey={key}&action=unsubscribeHook&hookUrl={url} to remove the webhook subscription, preventing orphaned webhooks and reducing unnecessary HTTP traffic.
GET /?zapierKey={key}&action=unsubscribeHook&hookUrl={url} to stop receiving lead notifications.
Multi-Channel Lead Distribution
Distribute leads captured by Palaccio to multiple destinations simultaneously - email, Slack, CRM, and Google Sheets - by subscribing multiple webhook URLs to the same Palaccio account. Each webhook fires when a new lead arrives, enabling parallel workflows like sales team notifications in Slack while logging to a spreadsheet and creating a CRM record.
Call GET /?action=subscribeHook&hookUrl={url} once per destination to register each webhook.
AI Agent for Lead Management Automation
Let an AI agent handle Palaccio lead workflows - fetching new leads, enriching them with external data, routing high-value leads to sales reps, and logging others to a nurture campaign. Through Jentic, the agent searches by intent (e.g., 'get palaccio recent leads'), loads the schema, and executes with the zapierKey injected securely.
Use Jentic search 'get recent palaccio leads' to find GET /?action=getRecentLeads, load schema, execute with zapierKey.
Key Endpoints
1 endpoints — palaccio zapier webhook api provides a single endpoint for managing lead data through zapier integrations.
METHOD
PATH
DESCRIPTION
GET
/
Execute Zapier action (getRecentLeads, subscribeHook, unsubscribeHook)
GET
/
Execute Zapier action (getRecentLeads, subscribeHook, unsubscribeHook)
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Palaccio Zapier Webhook API by hand means passing its API key as a query parameter against the Cloud Run webhook host and building your own retry and error handling. Through Jentic you install once, import the Palaccio Zapier Webhook API from the API Directory, store the key once, and your agent calls it.
Permission scoping
The Palaccio webhook takes its key and filters as query parameters rather than resource ids in the path, so limit the agent to the operations it needs, such as retrieving recent lead data. Webhook subscription changes are not included unless you add them.
Credential isolation
Your Palaccio key is stored once, encrypted, by your own Jentic One instance and injected as a query parameter at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get recent Palaccio leads' or 'subscribe to Palaccio webhooks', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Palaccio Zapier Webhook API through Jentic.
What authentication does the Palaccio Zapier Webhook API use?
The Palaccio API uses a zapierKey query parameter to authenticate requests. This key identifies the user account and is obtained from Palaccio's Zapier integration settings. Through Jentic, keys are stored encrypted and injected at execution time.
How do I subscribe to Palaccio lead webhooks?
Call GET /?zapierKey={key}&action=subscribeHook&hookUrl={url} to register a webhook URL. When new leads are captured, Palaccio will POST lead data to the provided URL.
Can I retrieve historical leads from Palaccio?
Yes. Use GET /?zapierKey={key}&action=getRecentLeads to fetch recent leads. The API returns an array of lead objects with name, email, phone, and metadata.
How do I unsubscribe from Palaccio webhooks?
Call GET /?zapierKey={key}&action=unsubscribeHook&hookUrl={url} to remove a webhook subscription and stop receiving lead notifications.
Is the Palaccio Zapier Webhook API free?
Palaccio is a lead generation service with various pricing tiers. The Zapier webhook API is available to Palaccio customers with Zapier integration enabled. Check palaccio.com for pricing details.
Can I subscribe multiple webhooks to the same Palaccio account?
Yes. You can call subscribeHook multiple times with different hookUrl values to distribute leads to multiple destinations simultaneously.
Can I limit what my agent is allowed to do with the Palaccio Zapier Webhook API?
Yes. Because you run Jentic One yourself, your own rules decide which Palaccio operations and credentials the agent can use, and this API passes its key and filters as query parameters rather than resource ids in the path. You can restrict the agent to just the calls it needs, such as retrieving recent leads with getRecentLeads, while excluding subscribeHook and unsubscribeHook so it cannot change webhook subscriptions. Only the operations you allow are exposed to the agent, and the Palaccio key is injected at execution time rather than placed in the agent's context.
GET STARTED