Display
Ecosystem
About five minutes of reading
Add the next system on a hook that already exists. Do not scrape the CCP and do not fork the flow for every vendor.
Hooks you can adopt later: EventBridge contact events, the CTR stream, agent events, Kinesis Video, Customer Profiles events, Cases, Show view, data tables, External Tool, and the flow language JSON in your pipeline. Live Sync and Agentic CX are the 2026 hooks for guided and agentic experiences.
A hook has a schema and a permission. Write both down when you 'leave room' for a vendor. Room without a schema is a hope.
Number on this page: Hooks 10. Events, streams, views, tables, tools, modules
Confirm before relying. Prices, quotas, and exam names change. Use the source linked on this page.
Picture from this room.
What usually goes wrong: A custom browser extension that clicks the CCP.
Which term matches this description? Prefer a module for a policy that every future flow must share.
Prefer a module for a policy that every future flow must share. The term is Future hooks, not future rewrites (3).
Connect Customer contact events - Amazon Connect Customer AWS docs. last checked 2026-10
Which term matches this description? A supported place to attach the next system: a stream, an event, a block, or a workspace view. Build on a hook instead of scraping the CCP.
A supported place to attach the next system: a stream, an event, a block, or a workspace view. Build on a hook instead of scraping the CCP. The term is Hook.
Connect Customer contact events - Amazon Connect Customer AWS docs. last checked 2026-10
Which term matches this description? The key that ties the flow log, the CTR, the recording, the agent event, and the CRM activity. Lose it and the ecosystem cannot be audited.
The key that ties the flow log, the CTR, the recording, the agent event, and the CRM activity. Lose it and the ecosystem cannot be audited. The term is ContactId join.
Integrate Amazon Connect with Amazon Kinesis | AWS re:Post community. last checked 2026-10
Connect Customer contact events - Amazon Connect Customer AWS docs. last checked 2026-10
The prose is a study paraphrase. The link is the source of the facts.
Connect answers the contact. Workforce, quality, emergency location, and the system of record sit beside it, and they only stay honest if they share ContactId.
A custom browser extension that clicks the CCP.
Adherence needs agent events, not a person refreshing a report. ResourceType AGENT_EVENTS and StorageType KINESIS_STREAM is the hook. A second consumer should read the stream, not a second delivery on the instance.
Resources:
AgentEvents:
Type: AWS::Connect::InstanceStorageConfig
Properties:
InstanceArn: !GetAtt CampusInstance.Arn
ResourceType: AGENT_EVENTS
StorageType: KINESIS_STREAM
KinesisStreamConfig:
StreamArn: !GetAtt AgentStream.Arn
Join records on ContactId. The integration map room lists the seams.
A CUCM calling search space is not a routing profile, but the profile is the closest idea of 'who can receive what'. A partition is not a Connect object. A UCCX CSQ and a UCCE skill group map to a queue. Precision steps map to routing criteria. A script, an Architect flow, and an Avaya vector map to a contact flow.
Hooks you can adopt later: EventBridge contact events, the CTR stream, agent events, Kinesis Video, Customer Profiles events, Cases, Show view, data tables, External Tool, and the flow language JSON in your pipeline. Live Sync and Agentic CX are the 2026 hooks for guided and agentic experiences.