Last active
December 18, 2015 04:59
-
-
Save justinvdm/5729683 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
var routing = { | |
channels: [{ | |
uuid: 'channel-uuid-1', | |
tag: ['apposit_sms', '*121#'], | |
name: '*121#', | |
description: 'Apposit Sms: *121#', | |
endpoints: [{uuid: 'endpoint-uuid-1', name: 'default'}] | |
}], | |
routing_blocks: [{ | |
uuid: 'routing-block-uuid-1', | |
type: 'keyword', | |
name: 'keyword-routing-block', | |
description: 'Keyword', | |
channel_endpoints: [{uuid: 'endpoint-uuid-2', name: 'default'}], | |
conversation_endpoints: [{uuid: 'endpoint-uuid-3', name: 'default'}] | |
}], | |
conversations: [{ | |
uuid: 'routing-block-uuid-2', | |
type: 'bulk-message', | |
name: 'bulk-message-1', | |
description: 'Some Bulk Message App', | |
endpoints: [{uuid: 'endpoint-uuid-4', name: 'default'}] | |
}], | |
routing_entries: [{ | |
source: {uuid: 'endpoint-uuid-1'}, | |
target: {uuid: 'endpoint-uuid-2'} | |
}] | |
}; |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@hodgestar Does it make sense for routing block models to have a
description
field as well (for eg'Keyword'
for a keyword routing block)?