Skip to content

Commit a349af2

Browse files
peterhurfordwilg
authored andcommitted
Fix link to Twilio example (#104)
* Fix link to Twilio * Fix the fix
1 parent d5a4211 commit a349af2

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎docs/adding_actions.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ When you've got those installed on your machine, run `yarn install` to install a
2222

2323
## Developing a new Action
2424

25-
Currently there are three places (`types`) of integrations – `query`, `cell` and `dashboard` level. The [Segment integration](https://github.com/looker/actions/blob/master/src/integrations/segment/segment.ts) is query level, which means it will attach to the scheduler. In the future, these will be able to attach to queries in Looker in other ways, but the integration shouldn't need to do anything differently to support that. The [Twilio Message integration](https://github.com/looker/actions/blob/master/src/integrations/twilio/twilio_message.ts) is a `cell` level integration and appears in Looker by adding a "..." to the end of each cell's data in the result table. Cell level integrations are essentially the same as our [existing "data actions"](https://discourse.looker.com/t/data-actions/3573), but provided via the integration API. These integrations will need to specify tag information in `requiredFields` and the relevant fields need to be tagged in some way via the [LookML `tags` parameter](https://docs.looker.com/reference/field-params/tags). The [SendGrid integration](https://github.com/looker/actions/blob/master/src/integrations/sendgrid/sendgrid.ts) is a dashboard level integration. These integrations support receiving an full dashboard image. An integration can also choose to hook into multiple types of actions if need be.
25+
Currently there are three places (`types`) of integrations – `query`, `cell` and `dashboard` level. The [Segment integration](https://github.com/looker/actions/blob/master/src/integrations/segment/segment.ts) is query level, which means it will attach to the scheduler. In the future, these will be able to attach to queries in Looker in other ways, but the integration shouldn't need to do anything differently to support that. The [Twilio Message integration](https://github.com/looker/actions/blob/master/src/actions/twilio/twilio_message.ts) is a `cell` level integration and appears in Looker by adding a "..." to the end of each cell's data in the result table. Cell level integrations are essentially the same as our [existing "data actions"](https://discourse.looker.com/t/data-actions/3573), but provided via the integration API. These integrations will need to specify tag information in `requiredFields` and the relevant fields need to be tagged in some way via the [LookML `tags` parameter](https://docs.looker.com/reference/field-params/tags). The [SendGrid integration](https://github.com/looker/actions/blob/master/src/integrations/sendgrid/sendgrid.ts) is a dashboard level integration. These integrations support receiving an full dashboard image. An integration can also choose to hook into multiple types of actions if need be.
2626

2727
To pass information about Looker users to the integration, you should specify [a `param`](https://github.com/looker/actions/blob/fd4ce4e63f44554c7257584df380f8a4e4adfc03/src/integrations/segment.ts#L18-L26) in the integration definition. When setting up the integration in Looker, the Looker administrator can choose to either type a value for the parameter or bind the value of the parameter to a particular User Attribute, which can be configured to provide whatever information you like on a per-user (or group) level.
2828

0 commit comments

Comments
 (0)