Email Octopus Contact (email_octopus_contact_v1
)
Replicate Email Octopus Contacts into your database.
To get set up, run this code from the WebhookDB CLI:
webhookdb integrations create email_octopus_contact_v1
Source documentation for this API: https://emailoctopus.com/api-documentation
Features
- Depends on
- To use this replicator, you will need email_octopus_list_v1. You'll be prompted to create it if you haven't.
- Supports Webhooks
- ❌
- Supports Backfilling
- ✅
Schema
Tables replicated from Email Octopus Contacts have this schema. Note that the data types listed are for Postgres; when replicating to other databases, other data types maybe used.
Column | Type | Indexed |
pk | bigint | |
compound_identity | text | ✅ |
email_octopus_id | text | |
email_octopus_list_id | text | |
email_address | text | |
status | text | |
created_at | timestamptz | ✅ |
deleted_at | timestamptz | |
row_updated_at | timestamptz | |
data * | jsonb |
* The data
column contains the raw payload from the webhook or API. In many cases there is no canonical form, like if a webhook and API request return two different versions of the same resource. In that case we try to keep the most coherent and detailed resource.”
Table definition
This definition can also be generated through webhookdb fixture email_octopus_contact_v1
.
CREATE TABLE public.email_octopus_contact_v1_fixture (
pk bigserial PRIMARY KEY,
compound_identity text UNIQUE NOT NULL,
email_octopus_id text,
email_octopus_list_id text,
email_address text,
status text,
created_at timestamptz,
deleted_at timestamptz,
row_updated_at timestamptz,
data jsonb NOT NULL
);
CREATE INDEX IF NOT EXISTS svi_fixture_compound_identity_idx ON public.email_octopus_contact_v1_fixture (compound_identity);
CREATE INDEX IF NOT EXISTS svi_fixture_created_at_idx ON public.email_octopus_contact_v1_fixture (created_at);