Skip to content

Commit a1491de

Browse files
committed
removed template language
1 parent b6fc61b commit a1491de

File tree

1 file changed

+1
-16
lines changed
  • src/connections/destinations/catalog/devrev

1 file changed

+1
-16
lines changed

src/connections/destinations/catalog/devrev/index.md

Lines changed: 1 addition & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,16 @@
11
---
2-
# The end name should be similar to `Slack Destination`
32
title: DevRev (Actions) Destination
43
hide-boilerplate: true
54
hide-dossier: true
65
id: 649adeaa719bd3f55fe81bef
76
---
87

9-
<!-- This template is meant for Actions-based destinations that do not have an existing Classic or non-Actions-based version. For Actions Destinations that are a new version of a classic destination, see the doc-template-update.md template. -->
10-
118
{% include content/plan-grid.md name="actions" %}
129

13-
<!-- Include a brief description of the destination here, along with a link to your website. -->
14-
1510
DevRev is a business software company that brings developers (dev) and customers (rev) together in the era of product-led growth. We are building an API-first dev-centric CRM that uses data, design, and machine intelligence to empower devs to build, support, and grow their revs. Learn more at [devrev.ai](https://devrev.ai){:target="\_blank”}, Twitter [@devrevinc](https://twitter.com/devrevinc){:target="\_blank”} and [Medium](https://medium.com/devrev){:target="\_blank”}.
1611

1712
The DevRev destination uses Segment's action framework to take action in your DevOrg when particular events or activity is sent from enabled Segment Sources.
1813

19-
<!-- In the section below, explain the value of this actions-based destination. If you don't have a classic version of the destination, remove this section. -->
20-
2114
## Use Cases of the DevRev Destination (Actions)
2215

2316
With this destination, website or external events can trigger action within DevRev.
@@ -46,12 +39,4 @@ By default, the `createRevUser` function will create a new RevUser (Contact) obj
4639
1. If the email address is a personal email address (defined by having a domain in the domain blacklist), then the Account will be searched for using the email address specifically (aka `[email protected]` would look for an account with external_ref of `[email protected]`)
4740
2. If the email address is a company address (defined by having a domain not in the domain blacklist), then we will look for an account with the company domain. If found, the RevUser will be created attached to this Account. If there is no existing account, a new one will be created with the company domain (aka `[email protected]` would be added under the Account with the domain `company.com`)
4841

49-
<!-- The line below renders a table of connection settings (if applicable), Pre-built Mappings, and available actions. -->
50-
51-
{% include components/actions-fields.html %}
52-
53-
<!--
54-
Additional Context
55-
56-
Include additional information that you think will be useful to the user here. For information that is specific to an individual mapping, please add that as a comment so that the Segment docs team can include it in the auto-generated content for that mapping.
57-
-->
42+
{% include components/actions-fields.html %}

0 commit comments

Comments
 (0)