Filters.

Email of the Contact.

Subject of the Note.

Description of the Notes.

Email of the Contact.

Tags to be added to the contact separated by comma. Tags can’t contain special chars except space and underscore.

The First name of the Contact.

Last name of the Contact.

Email Address of the Contact.

If there is a contact already in Agile with the given email, what should be done.

Phone Number.

Tags to be added to the contact separated by comma. Tags can’t contain number or special characters except space and underscore.

Name of the company.

Enter address line here.

Link website to a contact.

Name of the event.

Priority of the Event.

Owner of the event.

The starting time of the event.

End time of the event.

Subject of the task.

Type of the task.

Priority of the Task.

Owner of the task.

Email ID of the Contact.

Due Date of the Task.

This should return a list of dictionaries of content type JSON in reverse chronological order. For example: [{"id":1234},{"id":1235}]

If the returned JSON is not a list and is instead an object (maybe paginated), enter the key that contains the results. Example: "results", "items", "objects", etc... (children via dot syntax supported)

Zapier deduplicates the array we see each poll against the id key. If the id key does not exist, you should specify an alternative unique key to deduplicate off of. If neither are supplied, we fallback to looking for the shortest key with id in it otherwise we will raise an error.

If the content fetched is XML or HTML, optionally define an xpath to extract data from the content. Will trigger whenever the content at the xpath changes!

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

By default, Zapier gives you the entire payload of the webhook. If this is specified, Zapier will only grab the child key from the object(s) sent to Zapier. For example, given {"contact": {"name": "Mike"}}, add "contact" here to only return {"name": "Mike"}. Traverse more deeply nested children by using dot-separated syntax. Line item payloads will run your Zap for each instance of the child key.

We recommend not putting any query string arguments in the URL (use "Query String Params" below).

These params will be URL-encoded and appended to the URL when making the request. Note: If you specify nothing for this field, we will automatically encode and include every field from the previous step in the query string. If you don't want this, use the "Custom Request" action.

If "yes", this dumps the results directly to a key (set below) as JSON. If "no", we simulate a form.

Only used if As JSON.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

Any URL with a querystring will be re-encoded properly.

Pay special attention to the proper mapping of the data below.

These are key-value pairs that will form the data portion of the request. If you leave these empty, all fields from the previous step will be used. If you want to send your own raw JSON or form-encoded values here, please use the Custom Request action instead.

Wraps the request in an array if that is something the service requires.

A file object to be attached to the request. The request will automatically be converted to multipart/form-data, with the above payload type defining the sub content-type for the data being passed.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

Email of the contact.

Score to be added to the Contact in the AgileCRM.

Name of the Company.

URL of the company.

Name of the Deal.

Owner of the Deal.

Enter the probability of the deal.

Expected value of the deal.

Select the track for the deal from the given list.

Milestone of the Deal. The text should match an existing milestone for the selected Track (case sensitive).

The Email of the Contact.

Close Date of the deal.

Description of the Deal.

List of deal source option for a deal.

Email.

Subject of the ticket.

CC emails.

Priority.

Status.

Group name to assign.

Message.

Email address of the contact in the Agile CRM. It is used to identify which contact needs to be updated.

First name of the contact.

Last name of the contact in Agile CRM.

Company Name of the contact.

Phone Number of the contact.

Tags to be added to the contact. Multiple tags must be separated by comma.

Enter line address.

If no contact is present with the given email, should a NEW contact be created?

Link up a website to a contact.

The HTTP method we'll use to perform the request.

Any URL with a querystring will be re-encoded properly.

If yes, request data below will be overridden with the raw data from the previous step (you are still responsible for headers though, like Content-Type). Defaults to no.

Place raw data for the request here. Could be JSON, XML, etc. Nothing is parsed for you here (including extra line breaks or spaces -- everything is sent verbatim). You probably need to define a header below corresponding to your data Content-Type. Reminder: data provided in this field is completely ignored if you chose "yes" to pass-through.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

Any URL with a querystring will be re-encoded properly.

Pay special attention to the proper mapping of the data below.

These are key-value pairs that will form the data portion of the request. If you leave these empty, all fields from the previous step will be used. If you want to send your own raw JSON or form-encoded values here, please use the Custom Request action instead.

Wraps the request in an array if that is something the service requires.

A file object to be attached to the request. The request will automatically be converted to multipart/form-data, with the above payload type defining the sub content-type for the data being passed.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.