# Pipefy
## Using the Erathos platform
When selecting Pipefy as a new connector on the Erathos platform, you will need to name your connection and fill in the following form with a Service Account:
## How to create a Pipefy Service Account?
{% hint style="info" %}
Make sure you are a Super Admin in the organization before following those steps.
{% endhint %}
1. Click on the **name of your company** or your **profile image** at the top of the page. Then, click on **Members and Permissions**\
2. Click on the **Service Accounts tab**\
3. Click on **Create Service Account**\
4. Enter the Account Name. This will be used to create the email address and needs to be up to 20 characters.\
If you’d like, add a description. Up to 140 characters.
5. Define the role that this account will have on the organization.
6. Define how long tokens generated for this service account will work before they expire. The minimum time is 5 minutes and the maximum is 30 days.
7. Click on the Service Account on the list and get the Client ID, the Client Secret, and the token endpoint. **This is sensitive information,** so beware when sharing or storing it.
Don't forget to click on **Save and close** to advance to the next steps of the integration.
With this connection created you can seemlessly move your Pipefy data to your BigQuery, Redshift, Databricks or Postgres data-warehouse.
## What endpoints can I access with the Erathos platform?
* organizations
* pipes
* cards
* phases
* cards\_phases\_history
* tables
* tables\_records
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.erathos.com/connectors/apis/pipefy.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.