> For the complete documentation index, see [llms.txt](https://help.gleantap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.gleantap.com/integration/push-leads-to-abc.md).

# Push Leads to ABC

There are three ways to push leads to ABC<br>

1. **Form Workflow** - When a contact fills the form, you can have a workflow for “Webhook Call” within the form to push to ABC. This is set under Workflows > Webhook Call.<br>
2. **Form Redirect** - You can have a form redirect to the below URL with the parameters to submit to ABC.<br>
3. **Flows, via Webhook** - You can add a step to “Send to Webhook” to push to ABC.

\
The URL and parameters to be passed remain the same in each of the above ways. For Form Workflow & Form Redirect, ensure your form has the core attributes as mentioned at the bottom of this page.

If the lead already exists (based on the email) it will update the records in ABC instead of creating a new one.

### **Flow, via Webhook**

First, navigate to your flow list under **Flows** and click on the three little dots to edit your flow. The following steps will be the same if your are creating a new flow.&#x20;

Click the + to add an Action, and select 'Other.'

<figure><img src="https://312952119-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaFKpjLzPT7iDAWD0tQXo%2Fuploads%2FEdloCPEGJrumT0Gz89qD%2Fspaces_aFKpjLzPT7iDAWD0tQXo_uploads_9u0YMIYeCSmG5bRUwgFn_Screenshot%202023-10-13%20at%2012.webp?alt=media&amp;token=49d7ed1b-337a-46e1-bcd3-3f786f0ec91f" alt=""><figcaption></figcaption></figure>

<figure><img src="https://312952119-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaFKpjLzPT7iDAWD0tQXo%2Fuploads%2Fcn3DySWQU6vlXk8hF4FZ%2Fspaces_aFKpjLzPT7iDAWD0tQXo_uploads_yrQnTSSaGOlaVuIjR6qE_Screenshot%202023-10-13%20at%2012.webp?alt=media&amp;token=f122529a-7ff5-45d6-a302-2f12227f48e3" alt=""><figcaption></figcaption></figure>

Select 'Submit to Webhook' and enter the following information.&#x20;

**Webhook URL:**\
<https://api.gleantap.com/v1/Abcfinancial/addNewOrUpdateLead/app_id/club_id>

{% hint style="info" %}
**app\_id** is your workroom ID that shows up in the URL when you are on your dashboard. It looks something like *65788024711cb93776586fb2* (eg.)
{% endhint %}

**Method:**

GET

### **Data Attributes to Pass (Payload):**

* first\_name
* last\_name
* email
* phone, *optional*
* mobil&#x65;*, optional*
* address
* zip\_code
* gender
* birth\_date


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.gleantap.com/integration/push-leads-to-abc.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.