// kafka-connector options: START
[[camel-slack-kafka-connector-sink]]
= camel-slack-kafka-connector sink configuration

When using camel-slack-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:

[source,xml]
----
<dependency>
  <groupId>org.apache.camel.kafkaconnector</groupId>
  <artifactId>camel-slack-kafka-connector</artifactId>
  <version>x.x.x</version>
  <!-- use the same version as your Camel Kafka connector version -->
</dependency>
----

To use this Sink connector in Kafka connect you'll need to set the following connector.class

[source,java]
----
connector.class=org.apache.camel.kafkaconnector.slack.CamelSlackSinkConnector
----


The camel-slack sink connector supports 11 options, which are listed below.



[width="100%",cols="2,5,^1,1,1",options="header"]
|===
| Name | Description | Default | Required | Priority
| *camel.sink.path.channel* | The channel name (syntax #name) or slackuser (syntax userName) to send a message directly to an user. | null | true | HIGH
| *camel.sink.endpoint.iconEmoji* | Use a Slack emoji as an avatar | null | false | LOW
| *camel.sink.endpoint.iconUrl* | The avatar that the component will use when sending message to a channel or user. | null | false | LOW
| *camel.sink.endpoint.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | false | MEDIUM
| *camel.sink.endpoint.username* | This is the username that the bot will have when sending messages to a channel or user. | null | false | LOW
| *camel.sink.endpoint.webhookUrl* | The incoming webhook URL | null | false | MEDIUM
| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | false | MEDIUM
| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | false | MEDIUM
| *camel.component.slack.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | false | MEDIUM
| *camel.component.slack.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | false | LOW
| *camel.component.slack.webhookUrl* | The incoming webhook URL | null | false | MEDIUM
|===



The camel-slack sink connector has no converters out of the box.





The camel-slack sink connector supports 0 transforms out of the box, which are listed below.



[source,java]
----

org.apache.camel.kafkaconnector.slack.transformers.SlackTransforms

----



The camel-slack sink connector has no aggregation strategies out of the box.
// kafka-connector options: END
