Create integrations between Webhooks by Zapier and Evergiving to automate any workflow
WHEN THIS HAPPENS
Catch HookAUTOMATICALLY DO THIS
Create LeadEndless possibilities
How Zapier works
Zapier lets you build automated workflows between two or more apps—no code necessary. These workflows are called Zaps, and this is how they work.
A trigger is where automation begins
A trigger is an event that starts your Zap. Say you want to receive an email every time someone fills in a Facebook form—the trigger would be "new Facebook lead.
Now it's time for action
An action is the event an automation performs after it is triggered. Say you want to send a Slack message any time you receive a Facebook lead—the action would be "send a Slack message.
And that's it! You've just created a Zap.
A Zap is an automated workflow—consisting of a trigger and one or more actions—that connects your apps.
Connect your tools and unlock the power of automation
With Zapier's 6,000 integrations, you can unify your tools within a connected system to improve your team's efficiency and deepen their impact.
Choose a Trigger
Start here
Start here
Choose an Action
Supported triggers and actions
Zapier helps you create workflows that connect your apps to automate repetitive tasks. A trigger is an event that starts a workflow, and an action is an event a Zap performs.
URLRequired
Key
Deduplication Key
Xpath
Basic Auth
Headers
Try ItPick off a Child Key
Try ItURLRequired
Query String Params
Send As JSON
JSON key
Unflatten
Basic Auth
Headers
URLRequired
Payload Type
Data
Wrap Request In Array
File
Unflatten
Basic Auth
Headers
Catch Raw Hook
Wait for a new POST, PUT, or GET to a Zapier URL. Gives the request body unparsed (max 2 MB) and also includes headers.
Try ItMethodRequired
URLRequired
Data Pass-Through?
Data
Unflatten
Basic Auth
Headers
URLRequired
Payload Type
Data
Wrap Request In Array
File
Unflatten
Basic Auth
Headers
Allow Duplicates?
CountryRequired
Supporter First NameRequired
Supporter Last NameRequired
Lead Import LabelRequired
External Reference Number
Supporter Title
Supporter Email
Phone
Mobile Phone
Work Phone
Supporter Gender
Supporter Date of Birth
Private Notes
Validation Detail Comment
Address 1
City
State
Postcode
Campaign Name
Last Recurring Payment Amount
Last Recurring Payment Currency
Last Recurring Payment Date
Last Recurring Payment Frequency
Last Recurring Payment Method
Last Recurring Payment Method Other Type
Last Recurring Payment Failed
Last Recurring Payment Status
Last Recurring Payment Failed Reason
Total Number of Recurring Payments Made
Sum of Recurring Payments Made
Sum of Recurring Payments Made Currency
Highest Recurring Payment Made
Highest Recurring Payment Made Currency
Last Single Payment Amount
Last Single Payment Currency
Last Single Payment Date
Last Single Payment Payment Method
Last Single Payment Payment Method Other Type
Last Single Payment Failed
Last Single Payment Status
Last Single Payment Failed Reason
Total number of Single Payments Made
Sum of Single Payments Made
Sum of Single Payments Made Currency
Highest Single Payment Made
Highest Single Payment Made Currency
Previous Upgrade Date
Previous Upgrade Amount
Previous Upgrade Amount Currency
Last Contact Date
Last Contact Method
Product
Child Sponsored
Source
Source Campaign Name
Source Date
Source Time
Preference
Interest
Converstation Topic
Activity
Volunteered
Volunteered Type
Petition Signed
Petition Type
Appeal
Appeal Type
Event Participant
Event Participant Type
Campaigner
Supporter Timezone
Start Date
Validation Outcome Name
Validation Detail By
Validation Detail Date
Call Datetime
Call Outcome
Call Username
Final Call Outcome