AlertFind Airtable Connector

Looking to automate AlertFind Data Import? Yes! This is the place to be. Our Airtable Connector will make automation a breeze!

In order to perform a successful connection to your Airtable instance, we just need the following information and that's it! 

  1. API Key: The API Key can be generated/found under the API section on the Account Overview page using an Admin account. The account overview page can be reached by clicking on the User icon on the top right of the page.

  2. Base: The name of the Base from which you want to pull the information. Each of the square icons on your homepage is a different base.

  3. Table: The name of the Table from this Base, which has the required information. Each base can have one or more tables, which are similar to a single worksheet tab in a spreadsheet. Tables are used to hold a list of one particular type. 

Once we have a successful connection, it will enable us to populate your AlertFind instance with the fields available in that table. Some typical fields can be :

  • ID
  • Name
  • Phone
  • Position
  • Location
  • Status

How does our Airtable connector works :

The graphic below explains the various nodes involved in the transition of data from your Airtable instance to AlertFind.

Detailed Steps Explaining Graphic Above :

  1. Airtable connector fetches the User Information stored in your Airtable system via API.

  2. Based on your chosen frequency, our connector running on AWS Lambda fetches data from Airtable.

  3. At this stage, data goes through validation and processing and is transformed into a CSV.

  4. The CSV is compressed into a Zip file and sent to AlertFind API via the AlertFind connector running on AWS lambda.

Data Storage Nodes in The Graphic Above:

  1. Node 5 : Refers to Apache Cassandra Cluster which stores the data for execution purposes. It has a TTL of 7 days after workflow execution has finished.

  2. Node 6 : Refers to Elastic Search Cluster used for indexing data for 30 days so that it can be searched within the logs interface.

  3. Data Safety: All Data is encrypted in transit via HTTPS, using TLS 1.3 encryption internally. Sensitive customer data, such as access tokens, usernames and passwords are encrypted at rest using Amazon Key Management Service (KMS), which uses FIPS 140-2 validated hardware security modules.

We encourage you to keep searching the connector that suits your needs in our main AlertFind Connector List under the section System of Records Integrations by clicking the button below.

AlertFind Connector List