Skip to content

Commit 29827a5

Browse files
committed
Create Drip documentation index.md
1 parent 9f7687d commit 29827a5

File tree

1 file changed

+55
-0
lines changed
  • src/connections/destinations/catalog/actions-drip

1 file changed

+55
-0
lines changed
Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
# 💥 Segment Partner Actions Destination Documentation Template
2+
3+
> Hi Partners 👋🏼
4+
>
5+
> Welcome to Segment - glad to have you onboard! This doc serves as a guideline for your team to create best-in-class documentation alongside your amazing product.
6+
>
7+
> Here are the guidelines we want you to have in mind when writing out your documentation:
8+
>
9+
> - Be succinct and simple in your writing. Reduce text bloat where possible.
10+
> - Avoid 1st person language as it’s confusing for customers if they don’t know who wrote the docs (Segment or the Partner).
11+
> - Where pre-reading is required, hyperlink to other more generic parts of Segment’s (or your) documentation.
12+
>
13+
> - Screenshots/Images are generally discouraged unless absolutely necessary
14+
>
15+
> The below template intends to provide a standardized structure. To submit your documentation, complete the following steps:
16+
>
17+
> 1. Fork and clone the `segment-docs` repo locally
18+
> 2. Create a new branch (e.g., partner-name/destination)
19+
> 3. Create an `index.md` file in the following path `src/connections/destinations/catalog/{destination-slug}/index.md
20+
> 4. Copy the template below into your `index.md` file, and edit it to be in line with how your integration operates
21+
> 5. Add, commit, and push your code, then submit a pull request to the `segment-docs` repo
22+
>
23+
> If a section does not apply to your integration, feel free to remove. Please don’t create separate sections unless absolutely necessary. In most cases, creating a H3 (###) sub-heading under an existing section is the best option!
24+
>
25+
> If you have any questions in the meantime, please reach out to our team at [email protected].
26+
27+
## Template begins here...
28+
29+
---
30+
title: Drip (Actions) Destination
31+
---
32+
33+
{% include content/plan-grid.md name="actions" %}
34+
35+
[Drip](https://www.getdrip.com){:target="_blank”} is a nurture marketing platform Empowering B2C SMBs to convert long-sales cycle prospects into lifelong buyers with sophisticated and personalized marketing automation.
36+
37+
This destination is maintained by Drip. For any issues with the destination, [contact their Support team](mailto:[email protected]).
38+
39+
> (delete after reading) The section below explains how to enable and configure the destination. Include any configuration steps not captured below. For example, obtaining an API key from your platform and any configuration steps required to connect to the destination.
40+
41+
## Getting started
42+
43+
1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Drip".
44+
2. Select Drip and click **Add Destination**.
45+
3. Select an existing Source to connect to Drip (Actions).
46+
4. Go to the [Drip dashboard](https://www.getdrip.com/dashboard){:target="_blank"}
47+
5. In the Settings tab, select the User Settings, find and copy the **API key** at the bottom of the page.
48+
6. In a terminal, run `echo <your-api-key>: | base64` to encode the API key.
49+
7. Enter the encoded **API Key** in the Drip destination settings in Segment.
50+
8. Your account ID is a seven digit number that can be found in the address bar of your browser when you are logged into Drip. It is the number after `https://www.getdrip.com/`.
51+
9. Enter the **Account ID** in the Drip destination settings in Segment.
52+
53+
{% include components/actions-fields.html %}
54+
55+
For more information about developing with Drip, check out their [documentation](https://developer.drip.com/){:target="_blank”}.

0 commit comments

Comments
 (0)